-
-
Notifications
You must be signed in to change notification settings - Fork 85
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 API keys to be set by an environment variable #79
Comments
I don't really want to support arbitrary templating / complex configuration loading schemes (it's the reason json is chosen as the configuration format) |
Fair enough. What about an additional option then, e.g. |
feels like that'll open a bunch of new edge cases and error cases -- I'd really rather keep this simple, I don't think that checking in the configuration is the right answer here. If you want templating, you could always implement it with sed "s/API_KEY/${API_KEY}/g" all-repos.template.json > all-repos.json check in the template and a little wrapper script / make target / whatever and you're good to go |
plus you'll hit this wall with git-managed files: Line 38 in 252fe6f
|
OK, I'll just use the |
For anyone else who lands here, it looks like all-repos does now have support for reading API key from env vars =) b3d2d9e |
Use case: I'd like to add all-repos.json to source control without committing my API_KEY.
The text was updated successfully, but these errors were encountered: