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
Bug: Fn::GetAtt fails to resolve correctly #6868
Comments
Hey @morgan-dgk, like you mentioned, resolving that intrinsic isn't something currently supported. It is probably a good idea to document which cases are/aren't supported like you mentioned. Let me bring this to the team to see what we can do. |
Just wondering if there are any suggested workarounds for this currently? In my example, I would like to attach a Lambda Authorizer to a HTTP api using a lambda function defined in the SAM template like so:
However, as !GetAtt does not correctly resolve, this fails. |
This case should already be supported. Can you try changing the
to
|
Duh, apologies on my oversight. Debug log still shows this failing after correcting attribute name:
|
There also shouldn't be the colon after the
|
Ok, that seems to have fixed it. Thank you very much for your help. |
Description:
I am trying to use the GetAtt intrinsic function to retrieve the UserPoolId and ClientId from a UserPoolClient and UserPool resource respectively.
Debug output shows
Is this a supported feature currently or an area where Intrinsic Function support is limited?
If the latter, it would be great to document these limitations somewhere (unless I have missed them!)
Steps to reproduce:
Run
sam local invoke my_func
where some properties in template.yaml rely on Fn::GetAtt.Observed result:
Expected result:
!GetAtt should return the specified attribute for the given resource.
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
sam --version
: SAM CLI, version 1.113.0Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered: