Open tbenthompson opened 1 year ago
It looks like sops is correctly handling the env file to me from what you pasted here. --input-type
is about how the file is read, not about the format that the resulting encrypted file is written in. In your first example, you have to use both --input-type dotenv
and --output-type dotenv
to tell sops to load cloud/sops_kms/prod_secrets.gitignore
as a dotenv file, and write the encrypted result as a dotenv file as well.
Oh, I see! I hadn't noticed the --output-type
flag. Thanks for explaining. This feels like confusing behavior to me. I would expect the output format to default to being the same as the input format. But, I would also understand not wanting to break backwards compatibility.
First run with a
.gitignore
file extension. The file is not treated as an ENV file despite the--input-type dotenv
flag.Compare with a second run where I've renamed the file to have a
.env
extension: