mattcasters commented on PR #8780: URL: https://github.com/apache/hop/pull/8780#issuecomment-6062038931
We already went through this. Yes you need to do manual steps to enter passwords, configure things. That's the general consensus. Most environments have every data engineer in a team authenticate with their own username and password, for example. Surely that can't be too much of an issue? > When I set the variables with their defaults under Project → Environments, the values are stored in project-config.json and in the local environment file. For a secret this means the value is always committed: How can it be otherwise? Should the project be changed after an environment is implemented? That doesn't seem to make sense. Obviously it's clear to never store actual secrets in the project configuration nor in git. The notable exception there are passwords stored in a key-vault. I assume that will more and more become the standard. > Suggestion: for secret variables, keep only the name and description in project-config.json. Ask for the value when the environment is created and store it only in the local file, ideally with the existing Encrypted … mechanism. I considered it useful to have things like `Fill in the token you get from x` as hints for the person that needs to fill in the details. I'll look at the other comments when I find the time. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
