Nomad Variables

Path-addressed variables with compare-and-set writes, decrypted on read.

The connection

What	This provider
Vendor	HashiCorp
Key	`nomad-variables`
Availability	`available`. You can connect it today.
Credential penv holds	`nomad-token`
Values read back	yes
Activation	`on-next-deploy`

Direction	What it does
`import`	Reads names and values out of the store into penv.
`export`	Writes names and values from penv into the store.

on-next-deploy. A new value waits there and arrives with your next deploy.

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.

You paste a credential you already hold. penv seals it and never shows it again.

Field	Label	Kind	Required	What it is
`token`	ACL token	secret, masked here and sealed	yes	Needs variables:list, read, write and destroy in this namespace.

Fixed when you connect, and shared by every mapping on it.

Field	Label	Kind	Required	Advanced	What it is
`address`	Nomad address	text	yes	no	Must be reachable from the internet for us to write to it.
`namespace`	Namespace	text	no	yes	The ACL token's own namespace, if it is not default. Starts at `default`.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`pathPrefix`	Path prefix	text	yes	no	A sync owns one prefix. One penv secret is one variable path under it, and pruning deletes every path in reach, including ones this sync did not write.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`variables:list`	every direction	yes	Preview cannot list the paths under the prefix.
`variables:read`	`import`	yes	Import cannot read a variable's items.
`variables:write`	`export`	yes	Export cannot create or change a variable.
`variables:destroy`	`export`	yes	The overwrite_and_prune policy cannot remove a variable.