Error overriding secret values

[adiabuk]

As secret values can not be set in the override.json it seems possible to set secret values at the top level then overriding them with non-secret values seems possible (ie. the tool allows it). However when trying to access the subenvironment with get or process_templates gives the error:

trying to override key with secret value: key_name

The error would seem to be misleading as I am not overriding the key with a secret, but actually the opposite.

It would be useful to override secret to non-secret to allow creating a sub-environment without secrets, but similar in all other respects to the base env, without having to create a complete new environment.

[motns]

@adiabuk I'm trying to understand the use case for this: are you basically looking to re-use an environment in a place which doesn't have permission to decode the secret values in said environment?
The problem is that at the moment, when we process env and subenvs, we first load the top-level environment, and then apply overrides on top of it, so if you don't have permissions to load the secrets, you will get a failure.
For it to be useful, we'd need to do something hacky whereby we load all subenvironments first, and then bypass decoding of values for keys at the top level env, which also exist in a subenvironment...