-
Notifications
You must be signed in to change notification settings - Fork 421
Bug: Cannot fetch binary secrets #1713
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
Comments
Thanks for opening your first issue here! We'll come back to you as soon as we can. |
Thank you so much for flagging this @mangoes-git - our fault here for only accounting for String secrets, not Binary, as the response is different. What "transform='binary'" does is taking the value and decoding from base64 to bytes. If you'd like to contribute a bugfix, I can review and make any necessary amendments tomorrow morning (Amsterdam time). Otherwise I can read the docs tomorrow and make sure it's ready for our release this week. Thank you!! |
|
Expected Behaviour
parameters.get_secret
should fetch the secret and return it as a base64 decoded string.Current Behaviour
Throws
GetParameterError
. It seems it is trying to get the "SecretString" key instead of "SecretBinary" when passingtransform="binary"
Code snippet
Try to fetch the secret in Python
Possible Solution
No response
Steps to Reproduce
see the code snippet above.
AWS Lambda Powertools for Python version
latest
AWS Lambda function runtime
3.9
Packaging format used
PyPi
Debugging logs
No response
The text was updated successfully, but these errors were encountered: