-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(cli): support --no-rollback
flag
#16293
Conversation
CloudFormation recently released a feature that makes it easier to iterate quickly on development stacks, where the rollback step of a deployment is skipped if a deployment fails. This allows a developer to fix their code and retry quickly without losing time waiting for rollbacks. Fixes #16289.
@skinny85 I think this should be the default when running |
To disable the rollback feature, specify `--no-rollback`: | ||
|
||
```console | ||
$ cdk deploy --no-rollback |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I feel this deserves a short alias as well. Maybe -R
(stands for "rollback" or "retry")
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Thank you for contributing! Your pull request will be updated from master and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
CloudFormation recently released a feature that makes it easier to iterate quickly on development stacks, where the rollback step of a deployment is skipped if a deployment fails. https://aws.amazon.com/de/blogs/aws/new-for-aws-cloudformation-quickly-retry-stack-operations-from-the-point-of-failure/ This allows a developer to fix their code and retry quickly without losing time waiting for rollbacks. Fixes aws#16289. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
CloudFormation recently released a feature that makes it easier to iterate quickly on development stacks, where the rollback step of a deployment is skipped if a deployment fails. https://aws.amazon.com/de/blogs/aws/new-for-aws-cloudformation-quickly-retry-stack-operations-from-the-point-of-failure/ This allows a developer to fix their code and retry quickly without losing time waiting for rollbacks. Fixes aws#16289. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
CloudFormation recently released a feature that makes it easier
to iterate quickly on development stacks, where the rollback step
of a deployment is skipped if a deployment fails.
https://aws.amazon.com/de/blogs/aws/new-for-aws-cloudformation-quickly-retry-stack-operations-from-the-point-of-failure/
This allows a developer to fix their code and retry quickly without
losing time waiting for rollbacks.
Fixes #16289.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license