Google Secret Manager

Move secrets to and from a Secret Manager name prefix.

Connection

What	This provider
Vendor	Google Cloud
Key	`gcp-secret-manager`
Availability	`available`. You can connect it today.
Credential we hold	`gcp-service-account`
Values read back	yes
Activation	`immediate`

Direction	What it does
`import`	We read names and values out of the store into your environment.
`export`	We write names and values from your environment 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.

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

Field	Label	Kind	Required	What it is
`serviceAccountKey`	Service account key	secret; we mask it here and seal it	yes	The JSON key file for a service account with access to this project's secrets.

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

Field	Label	Kind	Required	Advanced	What it is
`projectId`	Project	text	yes	no	The project holding the secrets. One connection covers one project.
`basePrefix`	Base prefix	text	yes	no	The widest secret name prefix this connection may touch. Every sync scope will sit under it.

You answer these once per environment you map.

Field	Label	Kind	Required	Advanced	What it is
`namePrefix`	Secret name prefix	text	yes	no	Maps onto this environment. Pruning deletes the secret outright, and Google keeps no recovery window.

We probe for these when we verify the connection.

Permission	Directions	Blocking	Without it
`secretmanager.secrets.list`	every direction	yes	Preview cannot list what is under this prefix.
`secretmanager.versions.access`	`import`	yes	Import cannot read any value, because roles/secretmanager.editor does not include it.
`secretmanager.secrets.create`	`export`	yes	Export cannot add a key that is not there yet.
`secretmanager.versions.add`	`export`	yes	Export cannot write a value.
`secretmanager.versions.destroy`	`export`	no	Superseded versions stay, and keep billing.
`secretmanager.secrets.delete`	`export`	no	The overwrite_and_prune policy cannot remove remote keys.