added support for the ansible vault v1.2 payload format

[DictumMortuum]

Hello,

Thanks for the update to the original code. We're using the ansible vault payload format v1.2, which supports labels: https://docs.ansible.com/ansible/latest/user_guide/vault.html#ansible-vault-payload-format-1-1-1-2

Could you please check this PR?

Regards,
Dimitris

[clok]

Sorry for the delay in looking at this! Will take a look.

[clok]

@DictumMortuum Opened up this PR #12

Thank you for the submission. I really appreciate it. I wanted to add some more details to the update and prepare for integration with the Go port of ansible vault that I maintain as well (gwvault). Let me know your thoughts. There are some nuances that I will need to work out in gwvault that may result in some interface changes, but at the surface level, the Encrypt method will now support labels (vaultIDs) with that PR.

[DictumMortuum]

@clok The only reason that I created another Encrypt function was because I didn't want to break the API. I think that you can use variadic functions https://gobyexample.com/variadic-functions to avoid that as well, didn't thought of this before :)

[clok]

@DictumMortuum For sure. I was considering a major version bump to coincide with an interface change. Personally, I am not a fan of ordered parameters and rather structured interfaces. That would be a part of the version bump.

Variadic functions are useful, but in this case would rely on ordering to ensure they are used correctly. Good suggestion, but in this case I don't think it will be a good option.

I think the middle ground here is to create a new exported function (like you have done) and do a minor version bump. Then I will follow up with a major version update that uses an interface for structured parameters to the methods. I can then use that major version release in the gwvault tool to support these new features.

[clok]

@DictumMortuum Thank you for the contribution. Merged and published in v2.2.0

I will be following up with an interface changed as noted above.

[clok]

In case you are curious, here is a WIP PR for the v3 bump #13