-
-
Notifications
You must be signed in to change notification settings - Fork 4.3k
CFn: fix modelling issue with AWS::NoValue #13132
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
7f9c831
to
1b3d019
Compare
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 46m 48s ⏱️ Results for commit c21494b. ♻️ This comment has been updated with latest results. |
LocalStack Community integration with Pro 2 files ± 0 2 suites ±0 34m 4s ⏱️ - 1h 21m 41s Results for commit c21494b. ± Comparison against base commit 515c19b. This pull request removes 4098 and adds 4 tests. Note that renamed tests count towards both.
♻️ This comment has been updated with latest results. |
Test Results - Alternative Providers564 tests 329 ✅ 23m 45s ⏱️ Results for commit c21494b. ♻️ This comment has been updated with latest results. |
9791442
to
c21494b
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.
Thanks for fixing this!
Motivation
While investigating issues from the telemetry, I found that an
AWS::NoValue
was being turned into aNothing
which itself was being looked up as a key in a dictionary (the conditions).This does not work because
Nothing
is not hashable, so cannot be used as a dictionary key.The reason for this is that in #13000 I incorrectly set any
NoValue
toNothing
during the modelling phase, however this caused the above issue.Changes
arguments.value
toNothing
AWS::NoValue
in an update operation