Val Town

Push a penv environment into a Val Town val's environment variables.

The connection

What	This provider
Vendor	Val Town
Key	`valtown-env`
Availability	`available`. You can connect it today.
Credential penv holds	`valtown-token`
Values read back	no
Activation	`on-next-deploy`

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

Val Town returns no value once it holds one, so penv can write here and cannot read back.

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

Direction	Policies you can pick
`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`	API token	secret, masked here and sealed	yes	An API token with read and write access to your vals.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`valId`	Val	text	yes	no	The val whose environment variables this environment maps onto.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`vals:read`	every direction	yes	Preview cannot list the val's environment variables.
`vals:write`	`export`	yes	Export cannot write anything.