Automate Google Cloud Resource Manager
HumDay reads Google Cloud Resource Manager’s own published API description and derives 28 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Google Cloud Resource Manager is
Creates, reads, and updates metadata for Google Cloud Platform resource containers.
API host: cloudresourcemanager.googleapis.com
What HumDay can do in Google Cloud Resource Manager
14 documented operations change something in Google Cloud Resource Manager.
- POSTCreates a folder in the resource hierarchy.
/v3/folders - POSTCreates a new TagKey. If another request with the same parameters is sent while the original request is in process, the second request will receive an error. A maximum of 1000 Tag…
/v3/tagKeys - POSTCreate a Lien which applies to the resource denoted by the parent field.
/v3/liens - POSTRequest that a new project be created.
/v3/projects - POSTCreates a TagValue as a child of the specified TagKey.
/v3/tagValues - POSTCreates a TagBinding between a TagValue and a Google Cloud resource.
/v3/tagBindings - POSTMove a project to another place in your resource hierarchy, under a new resource parent.
/v3/{name}:move - POSTCreates a TagHold. Returns ALREADYEXISTS if a TagHold with the same resource and origin exists under the same TagValue.
/v3/{parent}/tagHolds - DELETEDeletes a TagHold.
/v3/{name} - PATCHUpdates the attributes of the TagValue resource.
/v3/{name} - POSTRestores the project identified by the specified name (for example, projects/415104041262).
/v3/{name}:undelete - POSTGets the access control policy for a TagValue.
/v3/{resource}:getIamPolicy - POSTSets the access control policy on a TagValue, replacing any existing policy.
/v3/{resource}:setIamPolicy - POSTReturns permissions that a caller has on the specified TagValue.
/v3/{resource}:testIamPermissions
What HumDay can read from Google Cloud Resource Manager
These are the operations a schedule or a trigger can watch.
- GETSearches organization resources that are visible to the user and satisfy the specified filter.
/v3/organizations:search - GETList all Liens applied to the parent resource.
/v3/liens - GETLists projects that are direct children of the specified folder or organization resource.
/v3/projects - GETReturn a list of effective tags for the given Google Cloud resource, as specified in parent.
/v3/effectiveTags - GETSearch for folders that match specific filter criteria.
/v3/folders:search - GETLists the folders that are direct descendants of supplied parent resource.
/v3/folders - GETLists all TagKeys for a parent resource.
/v3/tagKeys - GETLists all TagValues for a specific TagKey.
/v3/tagValues - GETLists the TagBindings for the given Google Cloud resource, as specified with parent.
/v3/tagBindings - GETRetrieves a TagKey by its namespaced name.
/v3/tagKeys/namespaced - GETRetrieves a TagValue by its namespaced name.
/v3/tagValues/namespaced - GETLists TagHolds under a TagValue.
/v3/{parent}/tagHolds - GETSearch for projects that the caller has both resourcemanager.projects.get permission on, and also satisfy the specified query.
/v3/projects:search - GETRetrieves a TagValue. This method will return PERMISSIONDENIED if the value does not exist or the user does not have permission to view it.
/v3/{name}
How automating Google Cloud Resource Manager works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Google Cloud Resource Manager account.
- Grant access, then go live. You approve the specific Google Cloud Resource Manager operations it may use — and only those.
Automate Google Cloud Resource Manager with these
- Gmail79 operations
- Google+9 operations
- Google Abusive Experience Report2 operations
- Google Accelerated Mobile Pages (AMP) URL1 operations
- Google Access Approval7 operations
- Google Access Context Manager9 operations
- Google ACME DNS2 operations
- Google Ad Exchange Buyer38 operations
- Google Ad Exchange Buyer II50 operations
- Google Ad Experience Report2 operations
- Google Admin SDK122 operations
- Google AdMob7 operations
Categories
Questions about Google Cloud Resource Manager automation
- Can HumDay connect to Google Cloud Resource Manager?
- Yes. HumDay reads Google Cloud Resource Manager's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 28 operations are documented.
- Do I need to write code to automate Google Cloud Resource Manager?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Google Cloud Resource Manager account.
- What can HumDay do in Google Cloud Resource Manager?
- 14 of the 28 documented operations change something in Google Cloud Resource Manager, and 14 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Resource Manager account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Google Cloud Resource Manager is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Resource Manager at cloudresourcemanager.googleapis.com/$discovery/rest?version=v3. Descriptions are the provider’s own words, not ours. Last published 2023-04-19.