Need to have secrets in tests of public jobs
The current way to have secrets in "test:" need that jobs are non-public. My need is to have secrets in environment of test shell of a public job, but hidden. (The problem is the display in job log/definition) The use of the secret file in overlay is fine for me.
So I have did a POC to send all dut-env.yaml in secrets and it works. So I have two choice:
- send all env in secrets and remove the old export in .bashrc (simplifying env handling)
- create a new dut-env.secret.yaml and send it in secrets. (and so keep the old du-env.yaml behavour)
What do you think ?
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information