-
Notifications
You must be signed in to change notification settings - Fork 4k
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
CfnMapping: Error when deploying template with mapping default value #28386
Comments
I didn't see the definition of your What if you change the |
btw, I noticed you are using node v21 which we haven't fully tested and we've seen some issues with v21. I would highly recommend fall back to v20 instead. |
Apologies for not including it in the original code snipppets.
In the synthesized template it appears to be correct:
|
Did you mean it synthesized correct but when you deploy, CFN fails with error? |
This issue has not received a response in a while. If you want to keep this issue open, please leave a comment below and auto-close will be canceled. |
Correct. |
Describe the bug
When attempting to deploy a stack that was successfully synthesized using the following code:
The synthesized template shows:
The change set validation/stack deployment fails with
Template error: every Fn::FindInMap object requires three parameters, the map name, map key and the attribute for return value.
I have also tried adding the map name:
According to the documentation my code appears to be correct.
Expected Behavior
The synthesized stack deploys successfully.
Current Behavior
The change set validation/stack deployment fails with
Template error: every Fn::FindInMap object requires three parameters, the map name, map key and the attribute for return value.
Reproduction Steps
Synthesize and attempt to deploy a template using code similar to:
Possible Solution
No response
Additional Information/Context
No response
CDK CLI Version
2.115.0 (build 58027ee)
Framework Version
No response
Node.js Version
21.4.0
OS
MacOS
Language
Python
Language Version
3.12.0
Other information
No response
The text was updated successfully, but these errors were encountered: