Reference
Google Secret Manager
Move secrets to and from a Secret Manager name prefix.
Move secrets to and from a Secret Manager name prefix.
The connection
| What | This provider |
|---|---|
| Vendor | Google Cloud |
| Key | gcp-secret-manager |
| Availability | available. You can connect it today. |
| Credential penv holds | gcp-service-account |
| Values read back | yes |
| Activation | immediate |
What it moves
| 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. |
When a written value goes live
immediate. The running app sees a new value at once.
What happens to a name that exists
| 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.
How you connect
You paste a credential you already hold. penv seals it and never shows it again.
| Field | Label | Kind | Required | What it is |
|---|---|---|---|---|
serviceAccountKey | Service account key | secret, masked here and sealed | yes | The JSON key file for a service account with access to this project's secrets. |
What the connection asks for
Fixed when you connect, and shared by every mapping on it.
| 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. |
What a mapping asks for
Answered 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. |
Permissions it needs
penv probes for these when it verifies 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. |
Related
Azure Container Apps
Secrets on a container app. A write replaces the whole set, so a concurrent portal edit is lost. A revision holds its old value until you restart or redeploy, and a referenced secret is never pruned.
Secret Manager (regional)
Secrets pinned to one Google Cloud region, readable only from that region.