`Invalid --set format` error when trying to set deeply nested value

[sylvorg]

`Invalid --set format` error when trying to set deeply nested value

[sylvorg]

Hmm... I may have misunderstood the use of set... My bad! I'll go ahead and close this!

[sylvorg]

No, wait... I think my question still applies!

[sylvorg]

Actually, what I'm trying to do is encrypt only a part of an otherwise unencrypted yaml file.

[felixfontein]

--set only operates on already encrypted files. It allows to modify a value in an sops encrypted file.

[sylvorg]

Is there any way to only partially encrypt an unencrypted file? Like, just the api_token in my example, and leave everything else?

[felixfontein]

Check out https://github.com/getsops/sops#48encrypting-only-parts-of-a-file.

Also the next release will allow to use comments to decide what to encrypt.

[sylvorg]

Check out https://github.com/getsops/sops#48encrypting-only-parts-of-a-file.

Ah; I'd forgotten about that. Thanks!

Also the next release will allow to use comments to decide what to encrypt.

Comments in the file to be encrypted, or in .sops.yaml?

[felixfontein]

Hmm, I'm sorry, actually it hasn't been merged yet. It's in #974.

[sylvorg]

Ah; is there a roadmap of sorts for 3.9.0 somewhere, or whichever release this feature will end up in eventually, perhaps? I'd like to subscribe to it, if possible!

[felixfontein]

I'm pretty sure it will end up in 3.9.0, but I have no idea when 3.9.0 will happen...

[sylvorg]

Fair enough; thanks for all the help! 😸