Deno Deploy: sync secrets

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

Connection

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

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

Deno Deploy returns no value once it holds one, so we 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.

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

Field	Label	Kind	Required	What it is
`token`	Access token	secret; we mask it here and seal it	yes	A Deno Deploy access token with access to this app.

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

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.

You answer these 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`.

We probe for these when we verify 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.