- Newest
- Most votes
- Most comments
following those steps :
a) dissociate st1 with dependents using native cfn
b) deploy the modified stack : st1
c) redeploy st2, st3, st4 to restore links between stacks
examples here :
This error means that you are exporting a value, and as part of the stack update, that value is being changed. Unfortunately, this cannot be done when those exported values are being used in other stacks, as there is no mechanism for cascading this change down to the other stacks that rely on the new value.
To get around it, you will need to update the other stacks to use a static value before you can update Myst1Stack
. After doing this, you can update these stacks to use the export again.
This documentation [1] describes a way to track this down via native CloudFormation. If these other stacks are also CDK, you can update these references in their CDK code, or you could modify the values temporarily in the CFN template to allow this update to go through, and then simply re-deploy the previous version of these stacks from CDK, as the needed metadata for CDK to link to your project will still be present.
[1] https://aws.amazon.com/premiumsupport/knowledge-center/cloudformation-stack-export-name-error/
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago