Automate Google Cloud Data Catalog
HumDay reads Google Cloud Data Catalog’s own published API description and derives 23 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 Data Catalog is
A fully managed and highly scalable data discovery and metadata management service.
API host: datacatalog.googleapis.com
What HumDay can do in Google Cloud Data Catalog
15 documented operations change something in Google Cloud Data Catalog.
- POSTCreates an entry. Only entries of 'FILESET' type or user-specified type can be created. Users should enable the Data Catalog API in the project identified by the parent parameter…
/v1beta1/{parent}/entries - POSTSearches Data Catalog for multiple resources like entries, tags that match a query.
/v1beta1/catalog:search - POSTCreates a tag on an Entry.
/v1beta1/{parent}/tags - POSTCreates a field in a tag template.
/v1beta1/{parent}/fields - POSTCreates a policy tag in the specified taxonomy.
/v1beta1/{parent}/policyTags - POSTCreates a taxonomy in the specified project.
/v1beta1/{parent}/taxonomies - POSTCreates a tag template.
/v1beta1/{parent}/tagTemplates - POSTImports all taxonomies and their policy tags to a project as new taxonomies.
/v1beta1/{parent}/taxonomies:import - DELETEDeletes a policy tag. Also deletes all of its descendant policy tags.
/v1beta1/{name} - PATCHUpdates a policy tag.
/v1beta1/{name} - POSTRenames an enum value in a tag template.
/v1beta1/{name}:rename - POSTReturns the permissions that a caller has on the specified taxonomy or policy tag.
/v1beta1/{resource}:testIamPermissions - POSTA maximum of 10,000 entry groups may be created per organization across all locations.
/v1beta1/{parent}/entryGroups - POSTGets the IAM policy for a taxonomy or a policy tag.
/v1beta1/{resource}:getIamPolicy - POSTSets the IAM policy for a taxonomy or a policy tag.
/v1beta1/{resource}:setIamPolicy
What HumDay can read from Google Cloud Data Catalog
These are the operations a schedule or a trigger can watch.
- GETGet an entry by target resource name.
/v1beta1/entries:lookup - GETGets a policy tag.
/v1beta1/{name} - GETLists tags assigned to an Entry.
/v1beta1/{parent}/tags - GETLists entries.
/v1beta1/{parent}/entries - GETLists all policy tags in a taxonomy.
/v1beta1/{parent}/policyTags - GETLists entry groups.
/v1beta1/{parent}/entryGroups - GETExports all taxonomies and their policy tags in a project.
/v1beta1/{parent}/taxonomies:export - GETLists all taxonomies in a project in a particular location that the caller has permission to view.
/v1beta1/{parent}/taxonomies
How automating Google Cloud Data Catalog 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 Data Catalog account.
- Grant access, then go live. You approve the specific Google Cloud Data Catalog operations it may use — and only those.
Automate Google Cloud Data Catalog 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 Data Catalog automation
- Can HumDay connect to Google Cloud Data Catalog?
- Yes. HumDay reads Google Cloud Data Catalog's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 23 operations are documented.
- Do I need to write code to automate Google Cloud Data Catalog?
- 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 Data Catalog account.
- What can HumDay do in Google Cloud Data Catalog?
- 15 of the 23 documented operations change something in Google Cloud Data Catalog, and 8 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Data Catalog 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 Data Catalog is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Data Catalog at datacatalog.googleapis.com/$discovery/rest?version=v1beta1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.