Red Hat Bugzilla – Bug 863629
set environment variables through command line
Last modified: 2014-06-18 03:25:24 EDT
Description of problem:
Right now the only possible way to set an environment variable is through a pre-hook, which requires the variables to be in git. If I can put them into git, I can put them into my code directly. The beauty of ENV variables is
a) I don't need a new commit just to change a variable
b) They are protected. I might have 20 developers of which NONE are allowed to know our database passwords and Facebook secret ids. git is NOT a solution to this kind of data.
Overall, git is not built to protect sensible information.
Version-Release number of selected component (if applicable):
latest as of today
for current recommendation and comments for flaws.
Idea / request
Steps to Reproduce:
We've got a story to cover this, and it's being tracked internally. We're working on getting the roadmap elements laid out online. Transferring to Krishna to organize and get slotted into the roadmap.
Tracking in US1821