Automate Google Cloud Private Catalog Producer
HumDay reads Google Cloud Private Catalog Producer’s own published API description and derives 19 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 Private Catalog Producer is
Enables cloud users to manage and share enterprise catalogs intheir organizations.
API host: cloudprivatecatalogproducer.googleapis.com
What HumDay can do in Google Cloud Private Catalog Producer
12 documented operations change something in Google Cloud Private Catalog Producer.
- POSTCreates a new Catalog resource.
/v1beta1/catalogs - POSTCreates an Icon instance under a given Product.
/v1beta1/{product}/icons:upload - POSTCreates a Product instance under a given Catalog.
/v1beta1/{parent}/products - POSTCreates a Version instance under a given Product.
/v1beta1/{parent}/versions - POSTCreates an Association instance under a given Catalog.
/v1beta1/{parent}/associations - DELETEHard deletes a Version.
/v1beta1/{name} - PATCHUpdates a specific Version resource.
/v1beta1/{name} - POSTCopies a Product under another Catalog.
/v1beta1/{name}:copy - POSTStarts asynchronous cancellation on a long-running operation.
/v1beta1/{name}:cancel - POSTUndeletes a deleted Catalog and all resources under it.
/v1beta1/{name}:undelete - POSTSets the IAM policy for the specified Catalog.
/v1beta1/{resource}:setIamPolicy - POSTTests the IAM permissions for the specified Catalog.
/v1beta1/{resource}:testIamPermissions
What HumDay can read from Google Cloud Private Catalog Producer
These are the operations a schedule or a trigger can watch.
- GETLists Catalog resources that the producer has access to, within the scope of the parent resource.
/v1beta1/catalogs - GETLists operations that match the specified filter in the request.
/v1beta1/operations - GETReturns the requested Version resource.
/v1beta1/{name} - GETLists Product resources that the producer has access to, within the scope of the parent catalog.
/v1beta1/{parent}/products - GETLists Version resources that the producer has access to, within the scope of the parent Product.
/v1beta1/{parent}/versions - GETLists all Association resources under a catalog.
/v1beta1/{parent}/associations - GETGets IAM policy for the specified Catalog.
/v1beta1/{resource}:getIamPolicy
How automating Google Cloud Private Catalog Producer 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 Private Catalog Producer account.
- Grant access, then go live. You approve the specific Google Cloud Private Catalog Producer operations it may use — and only those.
Automate Google Cloud Private Catalog Producer 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
Questions about Google Cloud Private Catalog Producer automation
- Can HumDay connect to Google Cloud Private Catalog Producer?
- Yes. HumDay reads Google Cloud Private Catalog Producer's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 19 operations are documented.
- Do I need to write code to automate Google Cloud Private Catalog Producer?
- 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 Private Catalog Producer account.
- What can HumDay do in Google Cloud Private Catalog Producer?
- 12 of the 19 documented operations change something in Google Cloud Private Catalog Producer, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Private Catalog Producer 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 Private Catalog Producer is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Private Catalog Producer at cloudprivatecatalogproducer.googleapis.com/$discovery/rest?version=v1beta1. Descriptions are the provider’s own words, not ours. Last published 2020-01-07.