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(AWS Deploy): Support disableRollback
parameter
#10236
feat(AWS Deploy): Support disableRollback
parameter
#10236
Conversation
Codecov Report
@@ Coverage Diff @@
## master #10236 +/- ##
==========================================
- Coverage 85.39% 85.37% -0.03%
==========================================
Files 339 339
Lines 13842 13843 +1
==========================================
- Hits 11821 11818 -3
- Misses 2021 2025 +4
Continue to review full report at Codecov.
|
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.
Thanks @fredericbarthelet - looks good, I only have minor remarks, let me know what do you think 🙇
bbd9df1
to
d75cc99
Compare
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.
Well done, thank you @fredericbarthelet 🙇
disableRollback
parameter
@@ -261,6 +261,7 @@ provider: | |||
stackParameters: | |||
- ParameterKey: 'Keyname' | |||
ParameterValue: 'Value' | |||
disableRollback: true # To be used for non-production environment |
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.
Why did you write "for non-production environment" here?
I think this param is to control a choice as to whether to attempt to fix a partial deployment, or to roll it all back. That's not necessarily tied to production or not.
"true" is required to work around AWS issues like aws-cloudformation/cloudformation-coverage-roadmap#573 , whether in production or non-production
Terraform has no-rollback as its default behaviour and plenty of people use that in production
Closes: #10235