Fly.io: sync secrets · Penv Cloud

Export secrets into a Fly app.

Connection

What	This provider
Vendor	Fly.io
Key	`fly-secrets`
Availability	`available`. You can connect it today.
Credential we hold	`fly-token`
Values read back	no
Activation	`on-request`

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

Fly.io returns no value once it holds one, so we can write here and cannot read back.

on-request. A new value waits there. We can deploy to activate it, and the sync form asks you first.

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

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

Field	Label	Kind	Required	Advanced	What it is
`orgSlug`	Organization	text	yes	no	Use an organization token (`fly tokens create org`). An app deploy token cannot list the org, so verify fails on it.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`appName`	App	text	yes	no	The app whose secrets this environment maps onto.
`deployAfterSync`	Restart machines after each sync	yes or no	yes	yes	Off, secrets reach machines started later. On, we restart them one at a time. Starts at `false`.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`apps:read`	every direction	yes	We cannot confirm the token reaches this organization.
`secrets:write`	`export`	yes	Export cannot write anything.