Compatibility Check the operation.
Check the operation.
Read the test.
See what v0.3.0, the last reviewed release (the latest is v0.4.0), verifies. Main currently matches it. Choose a service to see which operations are verified, what the backend serves and where a request stops.
Get started Choose your snapshot Start with the version
Start with the version
you use.
Coverage by service
Choose a service.
Open its matrix to find a specific call and the evidence attached to it.
v0.3.0 (last reviewed release)
1133 of 1227 RPCs Verified across
30 API surfaces, coverage table at
0ea2594.
main (from source, same as v0.3.0)
1133 of 1227 RPCs Verified across
30 API surfaces, coverage table at
0ea2594.
What the statuses mean
- Verified
- A merged test drives it through an official Google SDK.
- Served, not yet verified
- Answered by the backend; no test drives it yet.
- Refused
- Rejected with the field or reason named.
- Returns UNIMPLEMENTED
- The emulator says so explicitly.
- Not served
- This API is not served.
- Not claimed
- No test covers it, so CloudBurrow makes no claim.
What is still open
- docs/gaps.md lists every remaining gap in v0.3.0, grouped by
service with why it is open:
63 at
0ea2594. Most are error codes Google does not document, or behaviour an upstream emulator cannot provide. -
Some refusals are deliberate: Cloud Storage object IAM (ACLs are stored, not enforced), IAM enforcement
beyond the five checks that read stored policy,
signBlobas the instance's own account, and Cloud SQL IAM database authentication. They are listed as excluded on purpose.
What CI does not run
- Real-model inference tests include gated runs. The matrix and upstream notes identify which tests run on merges.
- Buildpacks and Functions Framework have dated CI evidence from gated tests.
Browse HTTP routes and schemas in Scalar. How statuses are assigned: docs/compatibility.md