Dynamically set sops.age_key

[srnnkls]

I have my private age key stored in 1password (but it could also live somewhere else). Now, I want to set the sops.age_key or MISE_SOPS_AGE_KEY dynamically like so:

# mise.toml

[env]
# second thing I tried
MISE_SOPS_AGE_KEY = "{{ exec(command='op read op://Employee/mise-demo/age_key', cache_key='age_key', cache_duration = '10s') }}"
_.file = ".env.yaml"

[tools]
age = "latest"
sops = "latest"

[settings]
# first thing I tried
sops.age_key = "{{ exec(command='op read op://Employee/mise-demo/age_key', cache_key='age_key', cache_duration = '10s') }}"
experimental = true

It seems that tera templates are not evaluated for sops settings? (Recursively) setting MISE_SOPS_AGE_KEY within mise's own env seems to come too late, though.

[gavriguy]

it would by nice if per project (in the mise.toml settings) we could override the auto mise activate and use something like:

op run --env-file yourscript.env -- mise activate as described here - https://developer.1password.com/docs/cli/secrets-scripts#option-1-use-op-run-to-load-secrets-into-the-environment

[gavriguy]

Another option is to have the _.file option available per task. This way it will be possible to use MISE_SOPS_AGE_KEY in the global env and then load the _.file per task