What ENV vars available to Atmos ?

[seanlongnyc]

We have some ENV vars one of our components needs and store them in 1pw. Seems that there is no 1pw store option for atmos at this time & I assume the 1pw cli is not contained in the default image so the TF provider cannot be used. We are using the git-actions-runner component to self-host our git actions in eks so we tried to use external-secrets-operator to pass the values into the container but the git-actions-runner only adds ENVs to the controllers and not runners. We have also tried adding them the the Git Actions environment but it appears the github_environment parameters is only an input for the apply and not the plan. What would the recommended path forward be?

[osterman]

What about doing something like this? Atmos supports an !exec function as well as an env section in the atmos.yaml and stack configurations.

See:

• https://atmos.tools/functions/yaml/exec/
• https://atmos.tools/functions/yaml/env/

You can use this in atmos.yaml and stack configuration.

env:
  FOOBAR: !exec "op read op://vault-name/secret-name"

[GabisCampana]

Hi @seanlongnyc,
Just following up here to see if you were able to move forward using the !exec + env approach Erik suggested above.

If this addressed your use case, could you please close the discussion as resolved? And if you’re still running into issues or need clarification on applying this with your GitHub Actions runners, let us know and we’re happy to dig in further.

Thanks.