We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ansible-vault supports vault identifiers already for a while. If a vault has an identifier, it will be automatically migrated to 1.2.
The encryption itself is not different, it is just the header.
According to https://github.com/tpickett66/ansible-vault-rb/blob/master/lib/ansible/vault.rb#L16 the lib is currently hard-checking for a 1.1 vault.
Docs about this from Ansible:
https://docs.ansible.com/ansible/latest/user_guide/vault.html#format-of-files-encrypted-with-ansible-vault
The text was updated successfully, but these errors were encountered:
No branches or pull requests
ansible-vault supports vault identifiers already for a while. If a vault has an identifier, it will be automatically migrated to 1.2.
The encryption itself is not different, it is just the header.
According to https://github.com/tpickett66/ansible-vault-rb/blob/master/lib/ansible/vault.rb#L16 the lib is currently hard-checking for a 1.1 vault.
Docs about this from Ansible:
https://docs.ansible.com/ansible/latest/user_guide/vault.html#format-of-files-encrypted-with-ansible-vault
The text was updated successfully, but these errors were encountered: