Deno Deploy

Push a penv environment into a Deno Deploy app's variables for one context.

The connection

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

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

Deno Deploy 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`	Access token	secret, masked here and sealed	yes	A Deno Deploy access token with access to this app.

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

Field	Label	Kind	Required	Advanced	What it is
`appId`	Application	text	yes	no	The app whose variables this environment maps onto. Layer syncs ignore it.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`context`	Context	choice	yes	yes	Deno keeps production, development and build as separate sets. One of Production, Development, Build. Starts at `production`.

penv probes for these when it verifies the connection.

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