Studio Project workflows for Google Cloud Compute Engine instances, disks, images, and networking
Google Cloud Compute Engine is Google Cloud's infrastructure-as-a-service offering for running virtual machines, persistent disks, images, and the virtual networking (VPC, subnets, firewalls, routes, load-balancing building blocks) that supports them.
This project provides OpenAPI specs for automating against the Compute Engine REST API via an Integration Model. The -latest spec is a curated subset covering common CRUD for automation — see OpenAPIs below.
| Asset | Description |
|---|---|
| OpenAPIs/ | Compute Engine REST API OpenAPI specs — curated -latest plus the full dated version |
| Studio Projects/Google Cloud Compute Engine | 27 workflows covering common CRUD automation |
| Requirement | Version |
|---|---|
| Itential Platform | 6.x |
| Google Cloud Compute Engine API | v1 |
| Google Cloud Compute Engine Integration Model | Required to build automation against the OpenAPI specs |
Import one of the OpenAPI specs from OpenAPIs/ as an Integration Model in Admin > Integrations, then create an integration pointing at https://compute.googleapis.com/compute/v1.
Authentication is a Bearer token in the Authorization header:
Authorization: Bearer <access_token> Use a Google service account access token with Compute Engine permissions (https://www.googleapis.com/auth/compute or https://www.googleapis.com/auth/cloud-platform scope). Generate one via Google Cloud IAM → Service Accounts.
The instance's authentication/server properties should look like this once configured:
{
"authentication": {
"Oauth2c": {
"client_id": "<your-client-id>",
"client_secret": "<your-client-secret>",
"token_url": "https://accounts.google.com/o/oauth2/token",
"refresh_url": "",
"scope": "",
"token": {
"access_token": ""
},
"authorization_url": "https://accounts.google.com/o/oauth2/auth"
}
},
"server": {
"protocol": "https",
"host": "compute.googleapis.com",
"base_path": "/compute/v1"
}
} | Spec | Version | Operations | Description |
|---|---|---|---|
google_cloud_compute_engine-latest.json | latest (curated) | 149 | Actively-maintained, curated for common CRUD automation — see breakdown below |
google_cloud_compute_engine-v1.json | v1 | 694 | Full spec for Compute Engine API v1 (694 operations) |
google_cloud_compute_engine-latest.jsonActively-maintained spec (x-vendor-api-version: v1). Trimmed to 149 of 694 upstream operations covering common CRUD for automation.
Resources included, by category:
See the repo README for the full scope and the full spec.
google_cloud_compute_engine-v1.jsonFull, unmodified vendor spec for Compute Engine API v1 (694 operations) — the vendor's complete API surface, preserved as-is. See google_cloud_compute_engine-latest.json above for the curated subset if you just need common CRUD automation.
Backed by the Google Cloud Compute Engine:latest Integration Model (see google_cloud_compute_engine-latest.json above). The project contains 27 workflows organized into 5 folders, one atomic workflow per API operation, covering the common-CRUD subset of the curated spec.
| Folder | Workflows | Scope |
|---|---|---|
| Instances | List, Get, Create, Update, Delete, Start, Stop Instance | VM instance lifecycle and power state |
| Disks | List, Get, Create, Update, Delete Disk | Persistent disk lifecycle |
| Networks | List, Get, Create, Update, Delete Network | VPC network lifecycle |
| Firewalls | List, Get, Create, Update, Delete Firewall | Firewall rule lifecycle |
| Images | List, Get, Create, Update, Delete Image | Machine image lifecycle |
| Dependency | Notes |
|---|---|
Google Cloud Compute Engine:latest Integration Model | Import from google_cloud_compute_engine-latest.json before importing the project |
Google Cloud Compute Engine integration instance | Create in Admin > Integrations with the connection properties above. Workflows are wired to an integration instance named Google Cloud Compute Engine — update the adapter_id value in each workflow task if yours is named differently |