awslabs / awslabs/aws-deployment-framework
[Feat]: Preserve Resource - Disable rollback of stack
- Dominant language
- Python
- Stars
- 699
- Forks
- 235
- Avg merge
- 20h 53m
- Merged PRs (30d)
- 7
Description
### Describe the feature
as per https://docs.aws.amazon.com/cdk/v2/guide/cli.html#cli-config
We are trying to trying to figure out how to set the -–disable-rollback / --no-rollback option so we can debug a stack that is failing to create
Apologies of this option already exists. Just found it hard to find where to set even when searching repo for
preserve
rollback
A CDK stack can have the param added to cdk.json but this stack is not using CDK. Its pure CF template so we think we need to add to the cli command that is executing the change set
### Use Case
We need to disable rollback so we can debug a stack that is failing to create. Specifically a stack with EC2 that we need cfn logs from
### Proposed Solution
allow flag in params file for stacks that are pure CF
### Acknowledgements
- [ ] I may be able to implement this feature request
Contributor guide
Research direction
Start with the parameter handling for pure CloudFormation stacks and trace the CLI command that executes their change set, using the AWS CLI documentation linked in the issue. Confirm how the framework currently deploys non-CDK stacks and where stack parameters are defined. Done means a pure CloudFormation stack can enable --disable-rollback or --no-rollback through its parameters and retain enough resources for debugging failed creation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, python
- Domain
- cloud, devops, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100