You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running sam local invoke if you are resolving secrets from secrets manager you do not get the secret you get the string placed in the template.yaml. When the function is deployed the string is resolved to it's actual secret value. Preferably invoking locally would give me the secret value im looking for.
Steps to reproduce:
Create a secret in secrets manager
Add said secret to your template.yaml like this for example: WSS_ENDPOINT: '{{resolve:secretsmanager:prod/wss/api:SecretString:endpoint}}'
Make sure to attempt to print out the environment variable.
run sam local invoke.
Observed result:
The print statement shows '{{resolve:secretsmanager:prod/wss/api:SecretString:endpoint}}'
Expected result:
The print statement should show wss://ldjslf382.execute-api.us-west-2.amazonaws.com/production
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
Windows:
SAM CLI, version 1.24.0:
AWS region: us-east-1
Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered:
Hey @devpresleycobb,
Thanks for the feedback. SAM CLI does not resolve remote resources for local invoke and adding support for each individual use case would be unmanageable. However, we are working on facilitating testing your project directly in the cloud with extremely fast local to remote syncs.
We would love to hear your opinion in our RFC for this new project: #3264
Comments on closed issues are hard for our team to see.
If you need more assistance, please either tag a team member or open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.
Description:
When running sam local invoke if you are resolving secrets from secrets manager you do not get the secret you get the string placed in the template.yaml. When the function is deployed the string is resolved to it's actual secret value. Preferably invoking locally would give me the secret value im looking for.
Steps to reproduce:
Observed result:
The print statement shows '{{resolve:secretsmanager:prod/wss/api:SecretString:endpoint}}'
Expected result:
The print statement should show wss://ldjslf382.execute-api.us-west-2.amazonaws.com/production
Additional environment details (Ex: Windows, Mac, Amazon Linux etc)
SAM CLI, version 1.24.0
:Add --debug flag to command you are running
The text was updated successfully, but these errors were encountered: