Skip to content
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

sanitize / in secret names #1470

Merged
merged 2 commits into from
Jun 30, 2023
Merged

sanitize / in secret names #1470

merged 2 commits into from
Jun 30, 2023

Conversation

oavdeev
Copy link
Collaborator

@oavdeev oavdeev commented Jun 30, 2023

Its not uncommon and even seems to be recommended by AWS to use / in AWS Secret Manager secret names. If used in conjunction with non-JSON secrets, it leads to issues here since we use secret name as environment variable name, and that can't contain /

Its not uncommon and even seems to be recommended by AWS to use `/` in AWS Secret Manager secret names. If used in conjunction with non-JSON secrets, it leads to issues here since we use secret name as environment variable name, and that can't contain `/`
@oavdeev oavdeev requested review from savingoyal and saikonen June 30, 2023 03:02
@savingoyal savingoyal merged commit 9a39bb9 into master Jun 30, 2023
@savingoyal savingoyal deleted the fix-secret-sanitization branch June 30, 2023 03:43
wangchy27 pushed a commit that referenced this pull request Jul 13, 2023
* sanitize / in secret names

Its not uncommon and even seems to be recommended by AWS to use `/` in AWS Secret Manager secret names. If used in conjunction with non-JSON secrets, it leads to issues here since we use secret name as environment variable name, and that can't contain `/`

* fix formatting
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants