-
Notifications
You must be signed in to change notification settings - Fork 655
New issue
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
Error with Vault single-variable encryption #263
Comments
I'll need to look into this works in Ansible. If anyone already knows and wants to fix this, just let me know. |
Ansible 2.3+ allows variables to be encrypted *within* YAML files. Pass vault_password (even if it's wrong) to the functions that parse YAML.
Ansible 2.3+ allows variables to be encrypted *within* YAML files. Pass a default vault_password to the functions that parse YAML. Include a test to check this raises no exceptions under Ansible 2.3+
@willthames I added a fix upon your |
I found when I put the vault string into Tower using the JSON formatter, that it converted the output YAML format as follows, which ansible-review approves of.
|
@deekayen I think it's that we use Ansible's YAML parser properly now, so both ansible-lint and ansible-review should now handle |
Yeah, disregard my comment from yesterday. I ran it today and it inserts the literal vault string into the template output instead of the parsed value. I upgraded to 3.5.0rc1 instead. |
Issue Type
Ansible and Ansible Lint details
Desired Behaviour
No error
Actual Behaviour (Bug report only)
When run against new vault string encryption (https://docs.ansible.com/ansible/playbooks_vault.html#single-encrypted-variable) files it fails with a YAML syntax error:
test.yml:
The text was updated successfully, but these errors were encountered: