Databricks secret scope

Secrets in a Databricks scope, written per key and pruned per key. Databricks never returns a value outside a cluster.

The connection

What	This provider
Vendor	Databricks
Key	`databricks-secret-scope`
Availability	`available`. You can connect it today.
Credential penv holds	`databricks-token`
Values read back	no
Activation	`immediate`

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

Databricks returns no value once it holds one, so penv can write here and cannot read back.

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

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 workspace access token, or an OAuth service-principal token.

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

Field	Label	Kind	Required	Advanced	What it is
`workspaceHost`	Workspace URL	text	yes	no	The address you sign in to. Must be reachable from the internet for us to write to it.

Answered once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`scopeName`	Scope	text	yes	no	The scope whose secrets this environment maps onto. Pruning deletes every secret in it, including ones this sync did not write.

penv probes for these when it verifies the connection.

Permission	Directions	Blocking	Without it
`READ`	every direction	yes	Preview cannot list the scope's keys.
`WRITE`	`export`	yes	Export cannot write anything.