feat: add config-bundle CLI commands - #1945
Open
nborges-aws wants to merge 1 commit into
Open
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## refactor #1945 +/- ##
============================================
+ Coverage 95.74% 95.80% +0.05%
============================================
Files 291 300 +9
Lines 16234 16547 +313
============================================
+ Hits 15544 15853 +309
- Misses 690 694 +4 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds imperative CRUDL and version listing commands for AgentCore evaluation configuration bundles:
eval config-bundle createeval config-bundle geteval config-bundle listeval config-bundle updateeval config-bundle deleteeval config-bundle version listSummary of changes
--componentsaccepts inline JSON,file://<path>, or stdin (-) viaSourceResolver.parseJsonFlagWithSchemautility.getcalls the latest-bundle API by default and the version API when optional--versionis provided.listreturns configuration bundles, whileversion listreturns all versions belonging to one bundle.updaterequires--id,--components, and--commit-message;--kms-key-arnremains optional. This counteracts the service API docs and smithy models, but is the confirmed validation structure in the service itselfparentVersionIdsentry, as required by service lineage validation.Type of Change
Testing
How have you tested the change?
Manually smoke tested all commands against a configuration bundle in my personal account:
bun run test(993 pass, 0 fail)I ran
npm run test:unitandnpm run test:integI ran
npm run typecheckI ran
npm run lintIf I modified
src/assets/, I rannpm run test:update-snapshotsand committed the updated snapshotsChecklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the
terms of your choice.