Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove incorrect statement in CDK v2 migration guide #446

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove incorrect statement in CDK v2 migration guide #446

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion v2/migrating-v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -331,7 +331,7 @@ Before deploying your stacks, use `cdk diff` to check for unexpected changes to
Expected changes include but are not limited to:
+ Changes to the `CDKMetadata` resource\.
+ Updated asset hashes\.
+ Changes related to the new\-style stack synthesis\. Applies if your app used the legacy stack synthesizer in v1\. \(CDK v2 does not support the legacy stack synthesizer\.\)
+ Changes related to the new\-style stack synthesis\. Applies if your app used the legacy stack synthesizer in v1\.
+ The addition of a `CheckBootstrapVersion` rule\.

Unexpected changes are typically not caused by upgrading to AWS CDK v2 in itself\. Usually, they're the result of deprecated behavior that was previously changed by feature flags\. This is a symptom of upgrading from a version of CDK earlier than about 1\.85\.x\. You would see the same changes upgrading to the latest v1\.x release\. You can usually resolve this by doing the following:
Expand Down