| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Allow use of consul-style forward slash env variables
Added tests for consul-style env vars
There was a problem hiding this comment.
Thanks for the PR
Sorry, something went wrong.
|
ANPewansmith please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information. @microsoft-github-policy-service agree [company="{your company}"]
Contributor License Agreement Contribution License AgreementThis Contribution License Agreement (“Agreement”) is agreed to by the party signing below (“You”),
|
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Problem
parseEnvLine uses /^\s*(_*[a-zA-Z]\w*)\s*=\s*(.*?)?\s*$/ to match env var names. \w only allows [A-Za-z0-9_], so keys containing / (e.g. globals/my_storage_dir=/some/path) are silently dropped — the line matches nothing and is discarded without error.
This affects users whose services use slash-namespaced config keys, a common pattern with Consul (used widely in enterprise deployments). The variables appear in the envFile but are silently ignored, when overriding Consul variables for local development this is extremely difficult to diagnose.
Fix
Change the key character class from \w* to [\w/]* to allow / in key names.
Notes