feat: multidoc support for yaml and json

[theurichde]

Description of the change

Add Support for Multidoc YAML and JSON, as stated in #114

Benefits

Users can have and manage multiple secrets in one file and encrypt those secrets in one run

Possible drawbacks

• This change does not apply to --merge-into

  • To use this with mutlidoc, we would need to specify a target secret. On the other hand, users can easily put their to-be-merged secret in a separate file

• Kind: List resources are not considered / supported

Applicable issues

• fixes When sealing multiple secrets in singe yaml file only first is sealed #114

Additional information

I want to get your opinion on this approach and see if I am on the right track here.

[theurichde]

Hi there 👋🏻

@alvneiayu @agarcia-oss @alemorcuq

I would like to have your feedback on this draft before raising the actual PR. Any thoughts on this approach?
Sealing & validating single and multi-doc secrets (either JSON or YAML) is implemented.

[alvneiayu]

thanks for your contribution @theurichde. Let me take some time to test it and review it. Again, thanks a lot.

[alemorcuq]

Thanks for the PR, @theurichde. Could you please check the failed linter job? The feature looks good!

[theurichde]

Hey there @alvneiayu @alemorcuq 👋🏻

Linting is fixed, should be green now.

I am wondering if we should put that feature somewhere (as a side note?) in the README? Maybe in the FAQ?

For Example:

Can I encrypt multiple secrets at once in one JSON / YAML file?
-> You bet you can! Drop as many secrets as you like in one file. Make sure to separate them via ---in YAML and as extra, single objects in JSON.

[alemorcuq]

Hey there @alvneiayu @alemorcuq 👋🏻

Linting is fixed, should be green now.

I am wondering if we should put that feature somewhere (as a side note?) in the README? Maybe in the FAQ?

Yep, I think that would be great!

[theurichde]

@alemorcuq I added a small block for multi doc support in the FAQ

[alemorcuq]

This is a great PR, @theurichde, thank you very much. It is ready to be merged but, due to some recent changes, a rebase is needed. Could you do that?

[theurichde]

@alemorcuq Thanks for reviewing! It's rebased and ready to rock 🤘🏻