-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
AWS SAM running local won't resolve FindInMap Intrinsic #2694
Comments
Thanks for the feedback. We will be adding this to our intake for prioritization. In the meantime, we highly recommend you to use SAM Accelerate to test this in your development environment in the cloud. Here is a helpful video to learn more about it, and here is the documentation for the beta feature. Please let us know if this helps with your testing needs. |
I am also experiencing this issue. It's not too bad for environment variables, as I can just overwrite them in the file passed to |
Any update on this? |
I came across an issue (reported here) where layers were not being included, and it was because I was using a mapping to provide the layer version. A SAM template is supposed to be an extension of a CloudFormation template, so it somewhat beggars believe that not all of the intrinsic functions that are available in a CF template can be used. Will this issue be fixed? If so, hopefully it will be soon. |
I've been stung by this issue again today, although with the For some it is not appropriate Please provide an update on the overarching issue of intrinsic functions not working with |
I've just noticed something weird. When I run
|
Description:
I can't make a template.yaml with Mappings work when testing locally, although they will deploy and work as expected.
Steps to reproduce:
sam init --runtime python3.8
template.yaml
sam build --parameter-overrides ParamaterKey=Environment,ParameterValue=test --use-container
sam local start-api --debug
, and it will show unresolved references.Observed result:
curl http://127.0.0.1/hello
and sam will show an error:Expected result:
There shouldn't be unresolved FindInMap causing exceptions, just as it doesn't happen with CloudFormation itself.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: 1.19.1 and 1.20.0The text was updated successfully, but these errors were encountered: