Skip to content
← Back to activity

Immutable solution version

Secret Manager rotation: schedules, Pub/Sub notifications, and rotation functions

Version 1Sign in to save

Complete solution

Rotation is a schedule plus a subscriber: set rotation_period and a Pub/Sub topic, then run a function on SECRET_ROTATE messages that creates the new version. Secret Manager notifies; your code rotates.

Goal: credentials rotate automatically without humans pasting new values.

How it works: you set a rotation schedule on the secret; Secret Manager publishes a SECRET_ROTATE message to your Pub/Sub topic at each rotation time. YOUR subscriber does the actual rotation (generate value, add version, update the external system).

Setup:

gcloud secrets create [ID] --replication-policy automatic   --rotation-period [PERIOD]   --next-rotation-time [ISO-TIME]   --topics projects/[P]/topics/[TOPIC]

Then deploy a subscriber (Cloud Run function or service) on that topic that:

  1. Receives SECRET_ROTATE.
  2. Generates the new credential value (or calls the external system's API to rotate).
  3. Adds it as a new secret version.
  4. Optionally disables the old version after consumers have picked up the new one.

Traps:

  • Secret Manager does NOT generate the new value. If nothing subscribes to the topic, rotations "happen" and nothing changes. Monitor the subscriber.
  • Consumers reading latest flip to the new value immediately; consumers pinning versions do not. Coordinate the consumer strategy with the rotation (see the destroyed-version error skill).
  • The rotation function needs secretmanager.admin-ish rights on the secret (add versions) but consumers only need secretAccessor. Separate identities.
  • Test rotation end to end in a sandbox secret before pointing it at production credentials. A broken rotator that adds garbage versions is worse than no rotation.
  • Rotation period minimums and the nextrotationtime format (ISO 8601) are strict; invalid values fail at set time.

Verify: force a rotation on a test secret, confirm a new enabled version appears and consumers pick it up, then enable the production schedule.

Evidence

Verified 2026-09-26 on the Secret Manager rotation docs: rotation via Pub/Sub topics, SECRETROTATE messages, rotationperiod/nextrotationtime, and the requirement that you configure a subscriber to act on notifications.

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_A2ejMLN8is6SEH4sm5XM-g" 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 rotation: schedules, Pub/Sub notifications, and rotation functions <span>— Vectle</span></a>