Secret Manager Secrets
Secrets with versions, replication policy, rotation schedules, expiry and accessor IAM.
Compare Secrets & Key Management across clouds →
Part of: GCP Production Landing Zone, GCP Kubernetes Platform
Verification
Live-testedReally deployed to a cloud sandbox, verified against its outputs and assertions, then destroyed - with the teardown confirmed.
Conformance
- Static validation (fmt · validate · tflint)
- Security scan clean (Checkov)
- Plan tests (mocked: validation rules · outputs)
Provenance
- SHA-256 checksum
- Cosign signature
Functional
- Live-tested - applied, verified, destroyed
Last verified 2026-06-30 · how we verify
Verify this download
cosign · sha-256Don't take our word for it. Every release is signed with cosign - check the bytes against our pinned public key before you trust them.
# 1. Our pinned public key - fetch once, trust out-of-band
curl -O https://www.iac-bazaar.com/cosign.pub
# 2. This module's Sigstore bundle
curl -o gcp-secret-manager-1.0.0.sigstore.json \
https://www.iac-bazaar.com/api/artifacts/gcp-secret-manager/signature
# 3. Verify the tarball you downloaded
cosign verify-blob \
--key cosign.pub \
--bundle gcp-secret-manager-1.0.0.sigstore.json \
gcp-secret-manager-1.0.0.tar.gz
# → Verified OK
# 4. (optional) confirm the checksum too
echo "70af2acc8868ab9e55250aea5989cb3dc04280c3defa06c91f8caf8b76ec1a7d gcp-secret-manager-1.0.0.tar.gz" | sha256sum -cUse it from the registry
terraform · opentofumodule "secret_manager" {
source = "www.iac-bazaar.com/iac-bazaar/gcp-secret-manager/gcp"
version = "1.0.0"
}Paid module — needs a purchase (or a subscription that covers it) plus a registry token from /account/tokens. Full setup: registry docs.
Inputs & outputs
Create a free account to read this module's contract
The declared contract — every input name, type, default and description, plus every output — is shown to signed-in accounts, not to anonymous visitors.
A free account sees the contract of every Free module. This one is Basic, so its contract unlocks when you buy it.
Documentation
gcp-secret-manager
A Secret Manager secret with a chosen replication policy (Google-managed
automatic by default, or user-managed regions with optional CMEK for
data-residency), an optional initial version that prefers the write-only
path so the value never touches state, optional expiry and rotation
notifications, and least-privilege accessor IAM. Works with Terraform
and OpenTofu (>= 1.6), Google provider >= 7.0, < 8.0.
Status: static-validated, live-test pending. Ships under live-test quarantine — validated with
tofu fmt,tofu validate, andtflint. Real apply → verify → destroy against a GCP project is pending a cloud sandbox.
Secure defaults
- No initial version by default — the value is set out of band (a
controller /
gcloud), so Terraform never owns plaintext. - Write-only seeding when you do seed —
secret_data_wo(Terraform 1.11+) pushes a value that is never persisted to state; the state-storedsecret_datapath is available but discouraged, and the two are mutually exclusive (enforced as a precondition). - Least-privilege accessor IAM —
accessor_membersare granted exactlyroles/secretmanager.secretAccessor(read-only) on this one secret, via additivegoogle_secret_manager_secret_iam_memberbindings. - CMEK-capable — user-managed replicas can be encrypted with your own KMS
key (
replica_kms_key_name); a precondition rejects CMEK with automatic replication, which uses Google-managed keys. - Recovery window —
version_destroy_ttlkeeps destroyed versions recoverable for a grace period. - Rotation is notification-only — Secret Manager pings a Pub/Sub topic on
schedule (a precondition requires
notification_topicswhen rotation is set); an external rotator mints the new value.
Requirements
- Terraform or OpenTofu
>= 1.6 hashicorp/google>= 7.0, < 8.0
License
Commercial — LicenseRef-IaCBazaar-Commercial.
Usage code & full reference unlock after purchase
The complete copy-paste usage, the full input/output reference, and operational notes ship with your licence - shown here and bundled in the download.
- Usage
- Inputs
- Outputs
Related modules
Certificate Manager (certificate map)
A Certificate Manager certificate map for external HTTPS load balancers, with an optional Google-managed certificate and DNS authorization provisioned when you supply a domain you control.
Cloud KMS Keyring & Keys
Keyrings and rotation-enabled crypto keys with per-key IAM for CMEK across GCS, BigQuery, Cloud SQL and disks.
Azure Key Vault
RBAC-mode Key Vault with private endpoint, diagnostics, and managed keys/secrets/certificates scaffolding.
KMS Key with Policy Patterns
Customer-managed KMS keys with sane key policies, aliases, rotation, and multi-region replicas.
Secrets Manager Secret
Secrets with versioning, resource policies, replication, and optional Lambda rotation scaffolding.
Vault Policies & Auth
Vault policies, auth backends, and secret engine configuration as code.