-
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
CFNV2: support CDK bootstrap and deployment #12967
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
Conversation
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 20m 11s ⏱️ Results for commit 416e809. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ±0 2 suites ±0 1h 43m 43s ⏱️ -39s Results for commit 416e809. ± Comparison against base commit 2d08a27. This pull request removes 1 and adds 3 tests. Note that renamed tests count towards both.♻️ This comment has been updated with latest results. |
b339278 to
fad779e
Compare
pinzon
left a comment
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 for tackling this! Now CDK should be usable with CFnV2
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.
Still don't get what happened. I didn't see it when I reviewed it the other day.
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.
comment: Nice. Now we have an updated version of the CDK template and still test for previous versions.
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 for fixing this!
Motivation
During my testing, even a simple CDK bootstrap failed to work against the engine. If we want to open the new engine up for testing, we should at least support the first CDK command a user will run.
The reason for the failure was mostly the messaging around performing a
DescribeStackson a stack that didn't exist. Because we didn't have 100% parity, the CDK CLI treated the failure to describe theCDKToolkitstack as a fatal error and terminated the process.Changes
Emulator changes
AWS::CDK::Metadataresource returns its physical resource id on updateFn::Ifis now short circuiting, meaning if it evaluates toTruethen we only visit theTruecase, and the same for theFalsecase!Sub ${Resource.Property}on a resource that has a falsey condition would lead to trying to look that resource up and failing (and therefore crashing)UsePreviousValuewhen supplying parameters (this is what the CDK does)deploy_cfn_templatenow supportsraw_parameterswhich allows forUsePreviousValueto be specifiedTesting changes
test_cdk.py::test_cdk_bootstraptest_cdk.py::test_cdk_bootstrap_redeploytotest_dynamic_resolving.pyas it got garbled in a previous PRTODO (follow ups)
Fn::AndandFn::Orbe short circuiting? What about other condition type intrinsic functions?