HashiCorp Vault: sync secrets

Move secrets to and from one Vault KV v2 path.

Connection

What	This provider
Vendor	HashiCorp
Key	`vault-kv`
Availability	`available`. You can connect it today.
Credential we hold	`vault-token`
Values read back	yes
Activation	`immediate`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment into the store.

immediate. The running app sees a new value at once.

Direction	Policies you can pick
`import`	`skip_existing`, `new_version`, `fail`
`export`	`create_only`, `overwrite`, `overwrite_and_prune`

How syncs work says what each one does.

Paste a credential from the vendor. We seal it and never show it again.

Field	Label	Kind	Required	What it is
`token`	Vault token	secret; we mask it here and seal it	yes	Vault tokens expire. A connection that verified today can be dead tomorrow with nothing changed here. Use a token with a lease long enough for your sync schedule, and renew it.

You set these when you connect. Every mapping on the connection shares them.

Field	Label	Kind	Required	Advanced	What it is
`address`	Vault address	text	yes	no	Must be reachable from the public internet over HTTPS.
`namespace`	Namespace	text	no	yes	Enterprise and HCP only. Leave empty for open-source Vault.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`mount`	KV mount	text	yes	no	Must be a KV version 2 mount.
`path`	Path	text	yes	no	One path per sync. Every key stored there is one secret here.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`read`	`import`	yes	Import cannot read the path.
`create`	`export`	yes	Export cannot write a path that does not exist yet.
`patch`	`export`	yes	Export cannot change a path without replacing everything else stored there.