Model a local project hierarchy.
Projects, a local organization, folders, tags and liens, from the registry every other service reads.
Backed by: CloudBurrow's project registry CloudBurrow
Get startedWhat it covers
Resource Manager is served alongside the local services. Its registry holds the projects, a fixed organization and folders, and other services read it: BigQuery serves every ACTIVE project in it. The official client tests cover hierarchy changes and the documented tag and lien operations. Policy records are useful for checking what a tool wrote. They do not decide who may call a local service.
- Create, get, search, update and delete projects through the v3 client
- A deleted project stays
DELETE_REQUESTEDfor 30 days and can be undeleted, as on Google (#1216) - Read one fixed local organization and manage its folders (#1294)
- Project moves, tag bindings and liens through the documented API subsets (#1295)
- Read and write supported IAM and organization-policy metadata, with IAM Conditions validated (#1368, #1745)
- Every ACTIVE project is also a BigQuery project (#1764)
What's verified
Follow the operation matrix to see what the backend serves and the tests linked to Verified calls.
Resource Manager v3 (Projects, Folders, Organizations, Tags)
54 of 54 RPCs Verified in v0.3.0
Resource Manager v1 REST (projects, org policies; liens on v1 and v3)
38 of 38 RPCs Verified in v0.3.0
Not supported
- 01 / Local boundary
The local organization is fixed. Creating another organization is outside the served scope.
- 02 / Local boundary
Stored policies and tags do not enforce permissions, apart from the five checks the IAM page names.
Source: docs/compatibility.md at main 0ea2594.
Questions
What proves the local hierarchy works?
Build against Google Cloud APIs, locally
Free and open source under Apache-2.0. No account, no sign-up, no Google Cloud bill.