mauriciofierrom / ansible-vault-nvim Goto Github PK

We could support decrypting whole files instead of just decrypting in-line variables.

Current implementation only supports top-level variables:

var: vault! |
  ...

We need to support multi-level variables:

vars: # for some reason
  nested1: !vault |
    ...
  nested2:
     moar_nesting: !vault |
       ...

A file with content like:

- some: "some"
   var: !vault |
          ANSIBLE...
- other: "other"
   var: !vault |
          ANSIBLE...

Returns a list of dicts with the variables (AnsibleSequences):

[{'some': 'some', 'var': 'a'}, {'other': 'other', 'var': 'a'}]

• Support configuring multiple vault ids and sources
• Support prompting for a password (?)

After encrypting a variable the multi-line encrypted content doesn't follow the literal style for block scalars:

Before:

level-1:
  sublevel-1:
    var-1: value
    unencrypted-value: value

After:

level-1:
  sublevel-1:
    var-1: value
    unencrypted-value: !vault |
    -------------------------------------
    -------------------------------------
    -------------------------------------

Where the dashes are the $ANSIBLE_VAULT block. This (naturally) causes parsing errors.

The YAML Specification states that only spaces are considered for indentation.

Currently, we store the decrypted values to files in the /tmp directory to be able to show them in a buffer from the location list. There must be a better way to do this to keep with the following guidelines https://docs.ansible.com/ansible/latest/user_guide/vault.html#vault-securing-editor