An undocumented assumption on encrypting yaml/json only

[consideRatio]

sops is able to encrypt arbitrary files, but has special support for yaml, json, and toml if I recall correctly. This action seem to have an undocumented assumption that can be broken for files that are encrypted but not yaml or json.

I suggest this assumption is made explicit in the readme.

[yuvipanda]

@consideRatio if you encrypt any file with sops, binary or otherwise, it gets converted into JSON! So all sops encrypted files are actually JSON or YAML (I didn't know it supported TOML).

[yuvipanda]

See https://github.com/2i2c-org/infrastructure/blob/master/eksctl/ssh-keys/openscapes.key for example. It's an ssh-key, so a plaintext file. Just gets converted to JSON automatically.

[consideRatio]

Thanks @yuvipanda for helping me de-confuse! Ping @sgibson91 who has been influenced by my past confusion.

1. sops can encrypt anything, but the encrypted file will be a JSON parsable file unless it was a YAML file initially, then it will remain a YAML file.
2. sops can not yet encrypt TOML, but probably in the future: add toml store getsops/sops#812

[yuvipanda]

@consideRatio yep! Hence it's always safe to assume that a sops encrypted file is parseable as YAML, no matter what - as all JSON is parseable as YAML too. This is very helpful in many places when you want to call in sops only if necessary - just parse the file regardless, and just pass it to sops only if there's a sops key in it! I use this quite a bit in hubploy...