Skip to content
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

De/Encrypt ansible-vault files when using "Resolve Conflicts" #104

Open
h1nds1ght opened this issue Jul 30, 2021 · 2 comments
Open

De/Encrypt ansible-vault files when using "Resolve Conflicts" #104

h1nds1ght opened this issue Jul 30, 2021 · 2 comments
Labels
enhancement New feature or request

Comments

@h1nds1ght
Copy link

h1nds1ght commented Jul 30, 2021

First of all thank you for your great plugin! It really makes handling of ansible vault files in PHPStorm very easy.

I also use the new feature by passing a vault password via the ANSIBLE_VAULT_PASSWORD_FILE environment variable, which works great.

But nevertheless there is one thing I miss so far. Maybe you know the problem, when merging 2 ansible vault files, it is hard to detect the differences. Normally if a merge conflict appears I use the "Resolve Conflicts" Feature of PHPStorm:

ui

Now, when I open this screen for a merge conflict Ansible-Vault file, everything (of course) is encrypted.

conflict

So my question is:

Would it be possible, when for example ANSIBLE_VAULT_PASSWORD_FILE is set and the vault files can be decrypted sucessfully with it to display it decrypted? And after solving the conflict the resulting file of course needs to be encrypted again.

@sadv1r
Copy link
Owner

sadv1r commented Jul 31, 2021

Thank you for the kind words I am happy you like it, and thank you for feature request.

I had some thoughts about showing decrypted vault data, for example like shown here.
At the same time I don't really sure if this feature is good, cause Vault may contain production data and some users don't want it to be shown without password when they don't expect it. It doesn't mean that this feature will not be implemented in some way, but I need more information about potential side effects

#26 #47

@sadv1r sadv1r added the enhancement New feature or request label Jul 31, 2021
@retoo
Copy link

retoo commented Jun 14, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants