The Secret Manager API, for code paths, not secrets.
Secrets and versions over gRPC and JSON on one port. Not a secret store: nothing is authenticated.
Backed by: CloudBurrow CloudBurrow
Get startedWhat it covers
Secret Manager is built by CloudBurrow and serves gRPC and JSON on one port, as Google’s endpoint does. It is not a secret store: nothing is authenticated. It exists so an application whose code reads Secret Manager runs locally.
- Secrets and versions
- Enable, disable, destroy and access versions
- gRPC and JSON on one port
- Environment variables for Cloud Run services
- Regional secrets and supported replication settings (#1453)
- Expiry, rotation schedules, notifications to Pub/Sub and list filters (#1225, #1228, #1259)
- Customer-managed keys for version payloads when local Cloud KMS is configured, including CMEK-protected versions mounted into Cloud Run (#1453, #1489)
In the console
Tested snippet
From docs/examples/ at main 0ea2594. CI runs these blocks against CloudBurrow.
import os, uuid, grpc
from google.cloud import secretmanager
from google.cloud.secretmanager_v1.services.secret_manager_service.transports import SecretManagerServiceGrpcTransport
channel = grpc.insecure_channel(os.environ["CLOUDBURROW_SECRETMANAGER_ENDPOINT"])
client = secretmanager.SecretManagerServiceClient(transport=SecretManagerServiceGrpcTransport(channel=channel))
secret = client.create_secret(parent=f"projects/{os.environ['GOOGLE_CLOUD_PROJECT']}",
secret_id=f"example-{uuid.uuid4().hex[:12]}",
secret={"replication": {"automatic": {}}})
client.add_secret_version(parent=secret.name, payload={"data": b"s3cret"})
assert client.access_secret_version(name=f"{secret.name}/versions/latest").payload.data == b"s3cret"
client.delete_secret(name=secret.name)
This block is run by CloudBurrow's Python suite in CI. If it stops working, CI fails. docs/examples/python.md
import assert from 'node:assert/strict';
import { randomUUID } from 'node:crypto';
import { SecretManagerServiceClient } from '@google-cloud/secret-manager';
import { grpc } from 'google-gax';
const endpoint = new URL(`http://${process.env.CLOUDBURROW_SECRETMANAGER_ENDPOINT}`);
const client = new SecretManagerServiceClient({
apiEndpoint: endpoint.hostname,
port: Number(endpoint.port),
sslCreds: grpc.credentials.createInsecure(),
});
const [secret] = await client.createSecret({
parent: `projects/${process.env.GOOGLE_CLOUD_PROJECT}`,
secretId: `example-${randomUUID()}`,
secret: { replication: { automatic: {} } },
});
await client.addSecretVersion({ parent: secret.name, payload: { data: Buffer.from('s3cret') } });
const [version] = await client.accessSecretVersion({ name: `${secret.name}/versions/latest` });
assert.equal(Buffer.from(version.payload.data).toString(), 's3cret');
await client.deleteSecret({ name: secret.name });
await client.close();
This block is run by CloudBurrow's Node.js suite in CI. If it stops working, CI fails. docs/examples/node.md
What's verified
Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.
Not supported
- 01 / Local boundary
Not a secret store: nothing is authenticated.
- 02 / Local boundary
IAM policies are stored, never enforced #365
Source: docs/compatibility.md at main 0ea2594.
Questions
Can I keep real secrets in it?
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.