-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Allow dash in environment variable names #6080
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for the pr :) I think we may need to split apart the sanitizing code path a bit in order to allow hyphenated variables without changing existing behavior.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks so much for taking another pass at this! I'm going to get one more set of eyes on this to make sure the NOMAD_
namespace for environment variables is sufficiently baked in that it covers all the generate cases.
…clean generate environment variables
@langmartin after thinking about it a bit more, I think only generated environment variables should be cleaned. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for submitting this. Fully agree that user set environment variables as set verbatim with no processing. Had a question about NOMAD_
prefix check heuristic but lgtm otherwise.
…clean generate environment variables
@notnoop I've added a specific list of the prefixes that needs to be cleaned, my only concern is for newly added generated environment variables prefixes that will need to be added to this list. |
@notnoop any update on this PR? |
Thanks @lchayoun , sorry for taking too long to merge. I'm less concerned about newly generated environment variables, considering that they don't have backward compatibility constraints like current ones. I'd follow up and add a comment for future contributors which I suspect is sufficient now. |
I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions. |
Fixes #6079