Sevalla

Sync a penv environment with a Sevalla application's environment variables.

The connection

What	This provider
Vendor	Sevalla
Key	`sevalla-app-env`
Availability	`available`. You can connect it today.
Credential penv holds	`sevalla-key`
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
`apiKey`	API key	secret, masked here and sealed	yes	An API key with applications:read, plus applications:write to export.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`applicationId`	Application	text	yes	no	The application whose variables this environment maps onto.

penv probes for these when it verifies the connection.

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