sops metadata not found should not be thrown for empty fileis

[cqjjjzr]

When running sops set or sops edit against an empty YAML file, an error sops metadata not found is returned. This make sense for non-empty files, but erroring on empty files make it hard to do "upsert" when generating SOPS files programmatically. For example, if I want to implement the following behavior, it would be awkward: Set field foo to bar in file foobar.yaml, and create a new one with foo=bar if foobar.yaml does not exist. I have to handle the update and create case completely separately.

Any ideas or workarounds are very appreciated.

[felixfontein]

Since you're creating files programmatically, check for an empty file before calling sops set, and call sops encrypt instead.

Also checking for empty (not non-existing) files is an extremely special use-case, which I don't think will ever be supported.