Open swoodford opened 7 years ago
I have the same issue, and this is strage, it was working right a few days ago and now I get this message
in the 1.2.0
release, the option to specify your ansible binary path has been added. Can you update and try to use the new option to see if that resolves your issue?
Seeing two new issues now:
When clicking "Sublime Text -> Preferences -> Package Settings -> Ansible Vault -> Settings":
When trying to run Ansible Vault Encrypt after entering Vault Password at the prompt and hitting enter:
First issue is just some inconsistency in how local dev and installed packages align. Can get that fixed pretty quickly.
For the second issue, what version of ansible are you using? Still 2.3.0.0
?
Hopefully this fixes the settings path bug: https://github.com/adambullmer/sublime_ansible_vault/releases/tag/1.3.1
I updated Ansible:
ansible --version
ansible 2.4.3.0
And updated the plugin to 1.3.1.
Settings issue fixed, now it will open but typing is not allowed in the settings file. I had to add it in the user settings file, maybe that is intentional?
Still seeing this error but now slightly longer:
The left side of the settings window is the package default, and is not editable. The right side is your user settings, and should be completely editable.
It looks like you're letting it prompt you for a password. I recommend you setup a password file and then configure the password_file
option.
It looks like the error is related to needing 2 inputs into the terminal command being run in the background. I'll need to spend some time to figure out how to fix that.
Trying to encrypt, decrypt or view any vault results in this Sublime Text error:
/bin/sh: ansible-vault: command not found
No option to set the path to Ansible in Preferences, Package Settings, Ansible Vault.
Ansible Vault working normally from terminal command line.
macOS Sierra: 10.12.3 (16D32) Ansible 2.3.0.0 Sublime Text 3 Build 3126