mirror of https://github.com/ansible/ansible.git
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
e396d5d508
Make !vault-encrypted create a AnsibleVaultUnicode
yaml object that can be used as a regular string object.
This allows a playbook to include a encrypted vault
blob for the value of a yaml variable. A 'secret_password'
variable can have it's value encrypted instead of having
to vault encrypt an entire vars file.
Add __ENCRYPTED__ to the vault yaml types so
template.Template can treat it similar
to __UNSAFE__ flags.
vault.VaultLib api changes:
- Split VaultLib.encrypt to encrypt and encrypt_bytestring
- VaultLib.encrypt() previously accepted the plaintext data
as either a byte string or a unicode string.
Doing the right thing based on the input type would fail
on py3 if given a arg of type 'bytes'. To simplify the
API, vaultlib.encrypt() now assumes input plaintext is a
py2 unicode or py3 str. It will encode to utf-8 then call
the new encrypt_bytestring(). The new methods are less
ambiguous.
- moved VaultLib.is_encrypted logic to vault module scope
and split to is_encrypted() and is_encrypted_file().
Add a test/unit/mock/yaml_helper.py
It has some helpers for testing parsing/yaml
Integration tests added as roles test_vault and test_vault_embedded
|
8 years ago | |
|---|---|---|
| .. | ||
| cli | 8 years ago | |
| contrib | 8 years ago | |
| errors | 9 years ago | |
| executor | 8 years ago | |
| inventory | 9 years ago | |
| inventory_test_data/group_vars | 9 years ago | |
| mock | 8 years ago | |
| module_utils | 8 years ago | |
| modules | 8 years ago | |
| parsing | 8 years ago | |
| playbook | 8 years ago | |
| plugins | 8 years ago | |
| template | 9 years ago | |
| utils | 8 years ago | |
| vars | 8 years ago | |
| __init__.py | 9 years ago | |