You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use ansible 2.9.11 and have set up the ansible.cfg to read a password file in my home directory.
Additionally, I use Sublimetext3 with this ansible_vault plugin, and I have the plugin configured to read the same password file.
Since the upgrade for ansible, I cannot encrypt any files anymore: I get the message ERROR! The vault-ids default,default are available to encrypt. Specify the fault-id to encrypt with --encrypt-vault-id.
This seems to be due to the fact that ansible-vault reads the ansible.cfg, spots the vault_password_file parameter, and creates a default vault-id; then it reads the command line options given in the plugin, which also creates a vault-id with the same name, and then it can't choose which one to use.
I can remove the line in ansible.cfg but that means all my CLI scripting stops working, so I don't want to do that.
If I remove the ST configuration line, this plugin asks me for the password, so that doesn't work either.
Is there a way to have the plugin detect whether there is already a default vault-id available and have it skip initializing another one?
Thanks!
The text was updated successfully, but these errors were encountered:
Hi.
I use ansible 2.9.11 and have set up the ansible.cfg to read a password file in my home directory.
Additionally, I use Sublimetext3 with this ansible_vault plugin, and I have the plugin configured to read the same password file.
Since the upgrade for ansible, I cannot encrypt any files anymore: I get the message
ERROR! The vault-ids default,default are available to encrypt. Specify the fault-id to encrypt with --encrypt-vault-id.
This seems to be due to the fact that ansible-vault reads the ansible.cfg, spots the vault_password_file parameter, and creates a default vault-id; then it reads the command line options given in the plugin, which also creates a vault-id with the same name, and then it can't choose which one to use.
I can remove the line in ansible.cfg but that means all my CLI scripting stops working, so I don't want to do that.
If I remove the ST configuration line, this plugin asks me for the password, so that doesn't work either.
Is there a way to have the plugin detect whether there is already a default vault-id available and have it skip initializing another one?
Thanks!
The text was updated successfully, but these errors were encountered: