-
Notifications
You must be signed in to change notification settings - Fork 421
fix(parameters): get_secret correctly return SecretBinary value #1717
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
Conversation
Thanks a lot for your first contribution! Please check out our contributing guidelines and don't hesitate to ask whatever you need. |
Codecov ReportBase: 99.27% // Head: 99.27% // Increases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## develop #1717 +/- ##
========================================
Coverage 99.27% 99.27%
========================================
Files 129 129
Lines 6056 6059 +3
Branches 402 403 +1
========================================
+ Hits 6012 6015 +3
Misses 20 20
Partials 24 24
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
thank you so much @mangoes-git - I've just added tests and a minor code style (removed else). Merging |
Awesome work, congrats on your first merged pull request and thank you for helping improve everyone's experience! |
Issue number: #1713
Summary
Changes
parameters.get_secret
can now fetch Binary Secrets.User experience
Before this patch, calling
parameters.get_secret
to get a Binary Secret will throw aGetParameterError
since it would only try to retrieve theSecretString
value from the secret value. Ref: #1713Now,
get_secret
will correctly fetch Binary Secrets.Checklist
If your change doesn't seem to apply, please leave them unchecked.
Is this a breaking change?
RFC issue number:
Checklist:
Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.