fix(profiles): return invalid state for malformed profile index (#176) - #184
Merged
Conversation
Surface corrupt KV profile index configuration as storeStatus invalid instead of masquerading as an empty profile list, and fail closed on profile-specific tools while keeping generic AWS tools unaffected. Closes #176 Co-authored-by: Cursor <cursoragent@cursor.com>
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
1 participant
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
storeStatus: "invalid"when the KV application profile index exists but contains malformed JSON or fails schema validation.Test plan
pnpm run typecheckpnpm testpnpm run test:integritypnpm run verify:connector-contractlist_application_profilesexposesstoreStatus: "invalid"anderrorlist_ec2_instancessucceeds with invalid profile index in contextCloses #176
Made with Cursor