fix: use correct resourceType for config bundle in E2E status test#1094
Merged
fix: use correct resourceType for config bundle in E2E status test#1094
Conversation
The status command outputs resourceType as 'config-bundle' (hyphenated) but the test was checking for 'configBundle' (camelCase).
github-actions
Bot
added
size/xs
|
Verified the fix against |
github-actions
Bot
removed
the
agentcore-harness-reviewing
jariy17
approved these changes
May 4, 2026
notgitika
added a commit
that referenced
this pull request
May 4, 2026
…1094) The status command outputs resourceType as 'config-bundle' (hyphenated) but the test was checking for 'configBundle' (camelCase).
3 tasks
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
3 participants
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.
Summary
configBundle→config-bundlein E2E status assertionThe
status --jsoncommand outputsresourceType: 'config-bundle'(hyphenated) but the test was matching against'configBundle'(camelCase), causing the status test to always fail with "Config bundle should appear in status: expected undefined to be defined".Test plan
config-bundle-eval-rec.test.tsstatus test should pass