ChristianWeissCG

Thanks for the report, i hope it will be fixed fast.

Yamldiff is **structure-aware**. Unix diff is **line-based**. I vote against a line-based "patch file format" for Yamldiff. Instead of `23,24c23,24` you can use a "patch file format" that uses a...

How many conflicts you get, depends on: - your workflow - frequency of parallel changes - the number of leave nodes in your yaml file Sops was designed which security...

ok, thanks for this detail. Having a plain text mac and a signature sounds like a better option as its purpose is to verify that nothing has changed, but not...

MAC is encrypted with AES_GCM. What i ask for is to not encrypt it, just calculate and then sign that MAC with e.g. GPG (https://www.gnupg.org/gph/en/manual/x135.html): > In addition to authenticating...

Thanks for the link. True. This should go to a separat ticket: #437

"--verify" is not required to implement a "sops auto merge conflict resolver", but it may prevents to commit broken sops files to branches (git hook), which will bring the "sops...

Just want to show my mental support to this request. I would love to see a `--load-additional-rules`. This would make it possible to share my company-custom helm chart best practice...

I do not think that it is required to add a new rule to the default ruleset (as disabled): https://github.com/adrienverge/yamllint/commit/1543d0e43556cd5165a7e785395964f9badfa404#diff-80ac6fe01633dda82861672967172ec9R42 because it would not get respected on exection of default...