Skip to content

add check for kms key in token vault before create one #427

add check for kms key in token vault before create one

add check for kms key in token vault before create one #427

Triggered via pull request February 18, 2026 21:24
Status Success
Total duration 3m 9s
Artifacts 1

build-and-test.yml

on: pull_request
Matrix: build
coverage
9s
coverage
Fit to window
Zoom out
Zoom in

Annotations

5 warnings
build (24.x)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
build (20.x)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
build (22.x)
No file matched to [**/uv.lock,**/requirements*.txt]. The cache will never get invalidated. Make sure you have checked out the target repository and configured the cache-dependency-glob input correctly.
coverage
Failed to read vite config file at /home/runner/work/agentcore-cli/agentcore-cli/vitest.unit.config.ts. Make sure you provide the vite-config-path option if you're using a non-default location or name of your config file. Will not include thresholds in the final report.
coverage
Unexpected input(s) 'coverage-thresholds', valid inputs are ['github-token', 'vite-config-path', 'json-summary-path', 'json-summary-compare-path', 'json-final-path', 'file-coverage-mode', 'file-coverage-root-path', 'working-directory', 'name', 'pr-number', 'comment-on', 'threshold-icons', 'comparison-decimal-places']

Artifacts

Produced during runtime
Name Size Digest
coverage-report
1.72 MB
sha256:0028cd7b6b19c2d67efb2028f69e01ebbd1929f8e1a6030dc455397fe288c2cc