Buckets and objects, with the edges tested.
Buckets, objects and Pub/Sub notifications, on CloudBurrow's own server for JSON, XML and gRPC.
Backed by: CloudBurrow's own server (v0.1.0 used fake-gcs-server) CloudBurrow
Get startedWhat it covers
Cloud Storage starts by default. CloudBurrow’s built-in server is the only Storage backend and serves all three transports on the same port. The official Go client tests write an object through gRPC and read it back through JSON, then check the reverse path. Methods the server has not built return an error naming the operation.
- Buckets and objects over the JSON API
- Resumable uploads, ranged reads, generation preconditions and compose
- Notifications to Pub/Sub
- Object versioning, soft delete, retention policies and holds
- Lifecycle rules, CORS, HMAC keys and XML multipart uploads
- JSON, XML and gRPC share one local store; tested gRPC reads and writes (#1321)
- Project-scoped bucket listing, managed folders, ACL metadata and bulk restore
- V2 and V4 signed URL verification, failing closed (#509)
- Signed URLs from IAM service accounts, verified against the certificates the instance's IAM Credentials serves for each account's own keys (#1787)
In the console
Tested snippet
From docs/examples/ at main 0ea2594. CI runs these blocks against CloudBurrow.
import uuid
from google.cloud import storage
client = storage.Client()
bucket = client.create_bucket(f"example-{uuid.uuid4().hex[:12]}")
bucket.blob("hello.txt").upload_from_string("hello")
assert bucket.blob("hello.txt").download_as_text() == "hello"
bucket.delete(force=True)
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 { Storage } from '@google-cloud/storage';
import { PassThroughClient } from 'google-auth-library';
const apiEndpoint = process.env.STORAGE_EMULATOR_HOST;
delete process.env.STORAGE_EMULATOR_HOST;
const storage = new Storage({
apiEndpoint,
projectId: process.env.GOOGLE_CLOUD_PROJECT,
authClient: new PassThroughClient(),
});
const [bucket] = await storage.createBucket(`example-${randomUUID()}`);
await bucket.file('hello.txt').save('hello', { resumable: false });
const [data] = await bucket.file('hello.txt').download();
assert.equal(data.toString(), 'hello');
await bucket.deleteFiles({ force: true });
await bucket.delete();
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.
Cloud Storage (JSON API)
83 of 86 RPCs Verified in v0.3.0
Cloud Storage (gRPC API v2)
29 of 30 RPCs Verified in v0.3.0
Not supported
- 01 / Local boundary
Signed URLs verify only against local keys. A URL signed here is accepted by no Google service.
- 02 / Local boundary
Bucket and managed-folder IAM and ACLs are stored without enforcing permissions.
- 03 / Local boundary
Object-level IAM answers 501. The coverage table distinguishes verified and implemented-only operations.
Source: docs/compatibility.md at main 0ea2594.
Questions
What backs Cloud Storage?
Are signed URLs checked?
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.