add a safety check to prevent clobbering non-CDK stacks

$ cdk --version 0.34.0 (build 523807c)

By default, the cdk CLI should refuse any command that would mutate a non-cdk stack. For example, {diff, synth} should be accepted but {deploy, destroy} should be refused. A command line switch and/or declaration in cdk.json could be implemented to override this check globally and perhaps also per-stack.

A stack could be identified as “CDK managed” by the presence of a resource of type AWS::CDK::Metadata.

[dhx-mike-palandra]

That’s a good observation, and generally your suggestions about IAM reflect best practice BUT they require a bit of advance planning.

My intent here is to suggest a safe guard for avoiding a potentially disruptive outcome: modifying a stack that was never managed by CDK before. Such an operation might be intentional but I believe it’s more likely to happen accidentally. As explained earlier, I believe such a change would be relatively simple to implement.

[github-actions[bot]]

This issue has not received any attention in 1 year. If you want to keep this issue open, please leave a comment below and auto-close will be canceled.