Hashicorp Vault: Make secret field configurable

[paullatzelsperger]

Feature Request

Currently, our Hashicorp Vault implementation requires that secrets contain their content in the form

{
  "content": "secret-value"
}

and the name of the field ("content") is hard coded.

We should make this configurable, to allow customizability and also allow storing multiple secret value per secret.

For example, this could come in handy when storing postgres credentials. We could then have one secret that contains both the user and password information:

{
  "pg-user": ...,
  "pg-pwd": ...
}

where now we would have to create two secrets, one for pg-user and one for pg-pwd, each containing a "content" field with the secret value.

Which Areas Would Be Affected?

Hashicorp Vault impl

Why Is the Feature Desired?

Flexibility, customizability

Solution Proposal

The current behaviour should remain the default. However, if the secret contains a "/", we split, and interpret the right side as property name inside the secret's JSON object.