-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
CloudFormation v2 Engine: Base Support for AWS::NoValue and Migration to Nothing Types #12668
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 - Alternative Providers971 tests 540 ✅ 21m 45s ⏱️ Results for commit 12e5705. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files 2 suites 21m 44s ⏱️ Results for commit 12e5705. ♻️ This comment has been updated with latest results. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 20m 58s ⏱️ Results for commit 12e5705. ♻️ This comment has been updated with latest results. |
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.
5 more passing tests, nice one
* Extends #12662
Motivation
The introduction of the CloudFormation v2 engine laid the foundation for a redesigned engine capable of accurately determining update requirements between CloudFormation deployments, while also enabling parallel execution during updates. However, the current implementation offers no support for
AWS::NoValue
pseudo parameter.Changes
AWS::NoValue
Maybe
andNothing
to signal missing valuesFuture Work
Add further boundary tests for the use of
AWS::NoValue
during update sequences.