docs(cli): document replacements and unwedging in Express Mode - #1970
Draft
sanjanaravikumar-az wants to merge 3 commits into
Draft
sanjanaravikumar-az wants to merge 3 commits into
sanjanaravikumar-az wants to merge 3 commits into
Conversation
Express Mode has rollback disabled by default, and CloudFormation does not perform replacement-type updates while rollback is disabled. Document that constraint next to the existing --no-rollback replacement note: how to deploy a replacing change (--express --rollback), why --rollback cannot rescue a stack that is already in UPDATE_FAILED, why cdk rollback is unavailable for express stacks, and how to unwedge such a stack by replaying the last successful configuration with --express --method=direct. Also notes why both flags are required for the replay, how to confirm up front that the replay really is a no-op, and that CloudFormation is expected to lift the restriction around 2026-11-15. Closes #1739
sanjanaravikumar-az
had a problem deploying
to
automation
September 18, 2026 05:59 — with
GitHub Actions
Failure
Contributor
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Scanned FilesNone |
This was referenced Sep 18, 2026
…le command If the failed resource is already at a new revision, restoring the previous configuration is itself a replacement and CloudFormation refuses it for the same reason. The page told those users to "deploy with rollback enabled instead", which is the one operation that provably cannot update a stack already in UPDATE_FAILED - it answers ValidationError: non-terminal [UPDATE_FAILED] - so a stranded reader following it literally got a second error and no next step. Say plainly that there is no known redeploy recovery for that case, and point at delete/recreate or AWS Support.
This branch had an error being deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #1739. Documents the Express Mode replacement constraint in the CLI README, next to the existing
--no-rollbackreplacement note.Replacement-type updates are not supported while rollback is disabled, which Express Mode does by default; CloudFormation classifies this as expected, so it is documented as a constraint rather than a defect. Covers deploying a replacing change with
cdk deploy --express --rollback, why that cannot update a stack already in UPDATE_FAILED, whycdk rollbackis unavailable for express stacks, and how to unwedge by replaying the last successful configuration withcdk deploy --express --method=direct— including why both flags are needed and how to confirm up front that the replay really is a no-op. Time-bound: CloudFormation is expected to lift the restriction around 2026-11-15.Every claim is backed by a real deploy. Code fix in #1969; related #1972. Draft pending sign-off from @lvielto, who owns this guidance.
#NNNNhere meansaws/aws-cdk-cli; noteaws/aws-cdk#1931is an unrelated closed issue.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.