Felix Fontein

No, my 9.x.y reference was to Ansible 9.x.y. That one has new releases for a year, as opposed to half a year as for other Ansible major release trains.

I'll close this since this has been resolved.

Thanks for your contribution! Please note that this is a **breaking change** and cannot be merged. There has been an earlier attempt at this (#622) that had to be reverted...

While it's definitely true that your implementation comes very close to not breaking backwards compatibility, there are some cases that are broken. One of them you yourself listed. Your claim...

Disabling the MAC *in general* (not as an optional escape hatch on decryption; for that we have the `--ignore-mac` option that should only be used if absolutely needed) is a...

@hurzelpurzel > sops do have an --output option as well, but I didn't get it to work. Maybe you can give it atry as well. Please note that `sops`'s command...

Please note that this is a breaking change and thus has no chance of being merged as-is.

> Yeah I tried to somehow detect if the user passed `--` after exec-env to only do it then, but I couldn't find a way to get that information out...

Even if `--` wasn't explicitly documented, it's a very common pattern for CLI parsers to that you kind of have to assume that users correctly guessed that they can use...

`sops exec-env` does not (and never did) interpret `{}`. `{}` is only used by `sops exec-file`. Not replacing `{}` by the filename pretty much wrecks `sops exec-file`, since you don't...