Automate Google Broker

What Google Broker is

The Google Cloud Platform Service Broker API provides Google hosted implementation of the Open Service Broker API (https://www.openservicebrokerapi.org/).

API host: servicebroker.googleapis.com

What HumDay can do in Google Broker

7 documented operations change something in Google Broker.

• POSTCreateBroker creates a Broker./v1beta1/{parent}/brokers
• DELETEUnbinds from a service instance./v1beta1/{name}
• PATCHUpdates an existing service instance./v1beta1/{name}
• POSTSets the access control policy on the specified resource./v1beta1/{resource}:setIamPolicy
• POSTReturns permissions that a caller has on the specified resource./v1beta1/{resource}:testIamPermissions
• PUTCreateBinding generates a service binding to an existing service instance./v1beta1/{parent}/service_bindings/{binding_id}
• PUTProvisions a service instance./v1beta1/{parent}/v2/service_instances/{instance_id}

What HumDay can read from Google Broker

These are the operations a schedule or a trigger can watch.

• GETGetBinding returns the binding information./v1beta1/{name}
• GETGets the access control policy for a resource./v1beta1/{resource}:getIamPolicy
• GETListBrokers lists brokers./v1beta1/{parent}/brokers
• GETLists all the bindings in the instance./v1beta1/{parent}/bindings
• GETLists all the instances in the brokers This API is an extension and not part of the OSB spec./v1beta1/{parent}/instances
• GETReturns the state of the last operation for the binding./v1beta1/{name}/last_operation
• GETLists all the Services registered with this broker for consumption for given service registry broker, which contains an set of services./v1beta1/{parent}/v2/catalog

How automating Google Broker works

1. Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
2. 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.
3. See it proven. The program runs and shows you the result before it is allowed near your live Google Broker account.
4. Grant access, then go live. You approve the specific Google Broker operations it may use — and only those.

Automate Google Broker 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 Broker automation

Can HumDay connect to Google Broker?

Yes. HumDay reads Google Broker's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 14 operations are documented.

Do I need to write code to automate Google Broker?

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 Broker account.

What can HumDay do in Google Broker?

7 of the 14 documented operations change something in Google Broker, and 7 read from it. HumDay only ever uses the specific operations your approved contract needs.

Is my Google Broker 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 Broker is held behind that approval.

Where this came from

The operations above are read from a published API description for Google Broker at servicebroker.googleapis.com/$discovery/rest?version=v1beta1. Descriptions are the provider’s own words, not ours. Last published 2020-01-07.