(cdk --context): add a --context-override flag for parameters

[ahoffmanzotec]

when using synth or deploy on a project that has an existing cdk.context.json file, the values entered in via the command line from the --context key=value should overwrite/override the existing values in the file if the --context-override flag is added.

Use Case

Allows for easier development of deploy pipelines in other products (like azure). Currently all of the values in the cdk.context.json file have to be updated via file manipulation. So if I have dedicated vpcs, kms keys, etc per environment or I have naming structures for resources that are based on environment naming, having those values in the context makes having dynamic stacks easier to create. However, currently all values in the cdk.context.json file must be updated via file manipulation, which is more work than necessary and a simple flag to indicate those existing values should be overwritten/overrode during synth/deploy time makes the most sense.

Proposed Solution

add a --context-override flag so identically keyed context pairs are overridden by parameters passed via cli instead of having the cdk.context.json file be the "arbiter of truth".

• 👋 I may be able to implement this feature request
• ⚠️ This feature might incur a breaking change

---

This is a 🚀 Feature Request

[peterwoodworth]

Hey @ahoffmanzotec, sorry for the long response time here.

#14948 is a similar issue, so I'll be closing this issue in favor of it. Please give it a thumbs up, and leave a comment too if you'd like 😄

[github-actions]

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.