fix(config): make AWS_MCP_APP_CONFIG optional in Wrangler configs (#175) - #183
Merged
Conversation
Remove the default app-config KV binding so users can deploy with only AWS_MCP_CACHE. Document optional profile setup and add contract tests. 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
AWS_MCP_APP_CONFIGfrom the defaultwrangler.jsoncso users can deploy with onlyAWS_MCP_CACHEwrangler.example.jsoncCloses #175
Test plan
pnpm run typecheckpnpm testpnpm run repo:safetypnpm run test:integritypnpm run output:guardrailpnpm run verify:connector-contractMade with Cursor