is it possible to use ENV vars to feed the spec in...
# atmos
p
is it possible to use ENV vars to feed the spec in atmos auth?
Copy code
auth:
    providers:
      azure-dev-ci:
        kind: azure/oidc
        spec:
          tenant_id: ${secret.tenant_id}
          client_id: ${secret.client_id}  # Dev SP
          subscription_id: ${subscription_id}
if not, this will be a good addition if the goal is to make Atmos fully VCS aware
e
Are tenant and client secrets in azure?
You can use
!env
to retrieve environment variables
But I would recommend instead creating a CI profile in atmos
p
I think they are not but some customers think they are
e
There's a bit of a catch 22 here. Not sure it makes sense to store these in a cloud secrets store
When it's the same secrets used for the configuration of the provider
while it could work with SOPS if we add that
p
yes
e
Is SOPS what you were thikning?
p
I have not think on solutions yet
but SOPS could be one