adambullmer / sublime_ansible_vault

Ansible vault manipulation in Sublime Text
MIT License
6 stars 2 forks source link

Ansible Vault: command not found #9

Open swoodford opened 7 years ago

swoodford commented 7 years ago

Trying to encrypt, decrypt or view any vault results in this Sublime Text error: /bin/sh: ansible-vault: command not found

image

No option to set the path to Ansible in Preferences, Package Settings, Ansible Vault.

Ansible Vault working normally from terminal command line.

which ansible
/usr/local/bin/ansible
ansible --version
ansible 2.3.0.0
  config file = 
  configured module search path = Default w/o overrides
  python version = 2.7.14 (default, Oct 18 2017, 12:03:25) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]
ansible-vault --version
ansible-vault 2.3.0.0
  config file = 
  configured module search path = Default w/o overrides
  python version = 2.7.14 (default, Oct 18 2017, 12:03:25) [GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]

macOS Sierra: 10.12.3 (16D32) Ansible 2.3.0.0 Sublime Text 3 Build 3126

GaboFDC commented 6 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

adambullmer commented 6 years ago

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?

swoodford commented 6 years ago

Seeing two new issues now:

When clicking "Sublime Text -> Preferences -> Package Settings -> Ansible Vault -> Settings": image

When trying to run Ansible Vault Encrypt after entering Vault Password at the prompt and hitting enter: image

adambullmer commented 6 years ago

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?

adambullmer commented 6 years ago

Hopefully this fixes the settings path bug: https://github.com/adambullmer/sublime_ansible_vault/releases/tag/1.3.1

swoodford commented 6 years ago

I updated Ansible:

ansible --version
ansible 2.4.3.0

And updated the plugin to 1.3.1.

image

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?

image

image

Still seeing this error but now slightly longer:

image

adambullmer commented 6 years ago

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.