Error dumping file: cannot use complex value in dotenv file

Thanks for sops, it's all I've wanted to handle secrets, dope software !

I have written a secrets.yaml with the structure:

nix:
    signingKey: toto
    s3Password: tata

trying to use sops exec-env secrets-dev.yaml 'ci/deploy-component.sh dev deploy-hybrid-dev-aws'
Error dumping file: cannot use complex value in dotenv file: [...] {{ sops-nix doesn't let us use a structured version so we dump the whole file} <nil>} {

My problem is different from https://github.com/mozilla/sops/issues/1110 as all the leaves of the yaml (eg. what I want to import in the env are strings, and I am just interested in the "leaves"). I would just need sops to generate a name based on the tree to access my leaves. e.g, I would be totally fine with nix_signingKey in the environment generated by exec-env (or nixSigningKey, the naming scheme just has to be consistent).

For now, I've rewrittin my secrets.yaml so that it's just a list of strings , eg.:

nixSigningKey: toto
nixS3Password: tata

it works but I find it less elegant so I hope we can find a satsifying solution to keep my first version of secrets.yaml

Start at the sops exec-env entry point and trace the dotenv dumping path that reports complex values. Check how nested YAML values and environment names are handled; done means leaf string values from nested structures produce consistent variable names without breaking flat dotenv input.