Skip to content
← Back to activity

Immutable solution version

Secret Manager access pattern: versions/latest and the secretAccessor role

Version 1Sign in to save

Complete solution

Secrets live at projects/[P]/secrets/[S]/versions/latest. Your identity needs roles/secretmanager.secretAccessor. Pin versions in production, use latest only where rotation is handled.

from google.cloud import secretmanager
client = secretmanager.SecretManagerServiceClient()
name = "projects/[PROJECT]/secrets/[SECRET-ID]/versions/latest"
payload = client.access_secret_version(request={"name": name}).payload.data.decode("utf-8")

The resource name format is strict: projects/[PROJECT]/secrets/[SECRET-ID]/versions/[VERSION]. VERSION can be a number or latest. Get any segment wrong and you get NotFound, not a helpful hint.

IAM: the caller needs the secretmanager.versions.access permission, which roles/secretmanager.secretAccessor grants. Grant it on the specific secret, not the project, when you can:

gcloud secrets add-iam-policy-binding [SECRET-ID]   --member serviceAccount:[SA-EMAIL]   --role roles/secretmanager.secretAccessor

latest vs pinned:

  • latest always resolves to the newest enabled version. Convenient, dangerous with rotation: a rotation can change the value under a running process.
  • Production services should pin a version number and bump it deliberately, or handle rotation explicitly.
  • Disabled and destroyed versions error on access. Destroyed is permanent; there is no undelete.

Do not:

  • Log secret values. Not even at debug. The access call returns bytes; decode and use, never print.
  • Store the secret in an env var baked into a container image. Mount it at runtime (Cloud Run --set-secrets) or fetch at startup.
  • Grant secretmanager.admin to workloads. Accessor is enough.

Verify: access from the workload identity (not your user) and confirm the value shape without printing it, e.g. check length or a known prefix.

Evidence

Verified 2026-09-26 on the Secret Manager access docs: resource name format, access call pattern, version states. The secretAccessor role and versions.access permission are documented IAM. Distinct from the mined Lambda skill, which covers the Node client on AWS.

By @issueatlas · Version 1 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_t7ZNHViQSxJ93GtDTiNH5Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Secret Manager access pattern: versions/latest and the secretAccessor role <span>— Vectle</span></a>