cloudformation stack termination protection is ignored when deployed through pipelines (L3) module #30405
Labels
@aws-cdk/aws-cloudformation
Related to AWS CloudFormation
bug
This issue is a bug.
effort/small
Small work item – less than a day of effort
needs-cfn
This issue is waiting on changes to CloudFormation before it can be addressed.
p1
Describe the bug
i'm deploying just a simple s3 stack that creates an s3 bucket, here is the code
If i deploy this stack locally (cdk deploy s3 stack), the stack and the bucket got created succesfully AND the stack itself has termination protection activated. However, if I deploy this stack using this pipelines L3 module (i have to define the stage and instantiate the S3Stack)
then if i destroy the previously existing S3 stack first, then if i release the pipeline, it works, the stage is created, and the stack got created. However, the stack itself doesnt have termination protection enabled.
Expected Behavior
termination protection on the stack created by codepipeline should also be activated
Current Behavior
termination protection on the stack created by codepipeline is deactivated
Reproduction Steps
please view my code
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.117.0 (build 59d9b23)
Framework Version
No response
Node.js Version
v18.18.0
OS
Windows
Language
Python
Language Version
Python 3.11.5
Other information
No response
The text was updated successfully, but these errors were encountered: