Automate Google Cloud Composer
HumDay reads Google Cloud Composer’s own published API description and derives 11 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 Composer is
Manages Apache Airflow environments on Google Cloud Platform.
API host: composer.googleapis.com
What HumDay can do in Google Cloud Composer
7 documented operations change something in Google Cloud Composer.
- POSTCreate a new environment.
/v1beta1/{parent}/environments - POSTCreates a snapshots of a Cloud Composer environment.
/v1beta1/{environment}:saveSnapshot - DELETEDeletes a long-running operation.
/v1beta1/{name} - PATCHUpdate an environment.
/v1beta1/{name} - POSTRestart Airflow web server.
/v1beta1/{name}:restartWebServer - POSTCheck if an upgrade operation on the environment will succeed.
/v1beta1/{environment}:checkUpgrade - POSTLoads a snapshot of a Cloud Composer environment.
/v1beta1/{environment}:loadSnapshot
What HumDay can read from Google Cloud Composer
These are the operations a schedule or a trigger can watch.
- GETList environments.
/v1beta1/{parent}/environments - GETList ImageVersions for provided location.
/v1beta1/{parent}/imageVersions - GETGets the latest state of a long-running operation.
/v1beta1/{name} - GETLists operations that match the specified filter in the request.
/v1beta1/{name}/operations
How automating Google Cloud Composer 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 Composer account.
- Grant access, then go live. You approve the specific Google Cloud Composer operations it may use — and only those.
Automate Google Cloud Composer 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 Composer automation
- Can HumDay connect to Google Cloud Composer?
- Yes. HumDay reads Google Cloud Composer's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 11 operations are documented.
- Do I need to write code to automate Google Cloud Composer?
- 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 Composer account.
- What can HumDay do in Google Cloud Composer?
- 7 of the 11 documented operations change something in Google Cloud Composer, and 4 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Google Cloud Composer 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 Composer is held behind that approval.
Where this came from
The operations above are read from a published API description for Google Cloud Composer at composer.googleapis.com/$discovery/rest?version=v1beta1. Descriptions are the provider’s own words, not ours. Last published 2023-04-21.