Keep a local record of enabled APIs.
The project-level Service Usage JSON API, with verified gcloud and Terraform examples.
Backed by: CloudBurrow's project registry CloudBurrow
Get startedWhat it covers
The always-served Service Usage endpoint lists what the local instance actually serves. gcloud and Terraform can record changes to a project’s enabled set. A request to enable an unavailable API is refused with a reason, so a successful settings call cannot imply a service is present when it is absent.
What's verified
Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.
Service Usage API (v1)
10 of 10 RPCs Verified in v0.3.0
Not supported
- 01 / Local boundary
Disabling an API changes its recorded state. The local API still answers calls.
- 02 / Local boundary
Enabling an API that this instance does not serve is refused. Folder and organization parents are outside the served scope.
Source: docs/compatibility.md at main 0ea2594.
Questions
Will a disabled API stop answering?
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.