-
Notifications
You must be signed in to change notification settings - Fork 97
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
Fixes the secrets parameter, adds the secret_env parameter #319
Conversation
LGTM |
@umohnani8 @jwhonce @baude PTAL |
Changes LGTM, but tests are unhappy |
Okay 👍 Thank you for looking into it. |
#320 is merged |
- Minor typo fix out of context: "example :" to "example:" - Secrets were not mounted correctly - Add parameter secret_env to mount secrets as environment variable Signed-off-by: André Peters <[email protected]>
Signed-off-by: André Peters <[email protected]>
Done @rhatdan |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: andryyy, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Minor typo fix out of context: "example :" to "example:"
The previous implementation of the secrets parameter allowed a string or Secret object to be defined.
The parameter passed to the API resulted in {"ID":str}.
While testing the secrets API I found that having only a single secret defined worked fine while more than one secret resulted in an exception:
The parameter ID was never used and a prefix of "" (empty) assumed.
Having a single entry in the Secrets Manager will always result in a single result, no matter the filter.
After losing myself in the API documentation, the correct data format I found is the following:
No changes for existing setups are necessary. Data (str, object, dict) is still expected within a list.
I added the secret_env parameter to set a secret's content as environment variable:
Inline documentation was updated. :-)