Prefect Cloud

Secret blocks in one Prefect Cloud workspace.

The connection

What	This provider
Vendor	Prefect
Key	`prefect-block-secret`
Availability	`available`. You can connect it today.
Credential penv holds	`prefect-key`
Values read back	yes
Activation	`immediate`

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.

immediate. The running app sees a new value at once.

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 account or workspace API key. A service account key survives the person who made it.

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

Field	Label	Kind	Required	Advanced	What it is
`accountId`	Account ID	text	yes	no	The first ID in your Prefect Cloud URL, after /account/.
`workspaceId`	Workspace ID	text	yes	no	The second ID in the same URL, after /workspace/.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`namePrefix`	Block name prefix	text	yes	no	A workspace holds every block in one list, so the prefix is what this sync owns.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`Workspace Viewer`	every direction	yes	Preview cannot list the Secret blocks in this workspace.
`Workspace Developer`	`export`	yes	Export cannot write anything.