Skip to main content
Use google_workspace in twins and put this configuration under seed_config.google_workspace. Google Workspace Admin SDK Directory users, groups, memberships, organizational units and tenant domains, People contacts, Workspace Events subscriptions, Apps Script projects, and Pub/Sub delivery resources.

Example seed

This is the complete Scenario request body for creating a Scenario. You can also import it with arga test-runner scenarios import --file scenario.json.

Parameters

The following fields belong directly inside seed_config.google_workspace. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.

Resource fields

These tables describe the record shapes used by the example. Keep native field names and casing. Map keys such as property names, IDs, and metadata keys are supplied by your fixture.

contacts[]

contacts[].names[]

contacts[].emailAddresses[]

scripts[]

scripts[].files[]

pubsub_topics[]

pubsub_topics[].subscriptions[]

event_subscriptions[]

API coverage and limitations

Twin name: google_workspace CLI quickstart: Use the Google Workspace CLI with Arga twins Supports
  • Google People v1 contacts, contact groups, other contacts, profile reads, and search.
  • Google Workspace Events v1 subscriptions, operations, reactivation, event-type filters, task streams, and push-notification helpers.
  • Google Apps Script v1 projects, content, versions, deployments, processes, and script execution.
  • Cloud Pub/Sub topic, subscription, pull, acknowledge, and IAM helpers used by Workspace event workflows.
  • People, Workspace Events, and Apps Script Discovery documents.
Known limitations
  • This grouped API-only twin does not publish Drive, Docs, Sheets, Gmail, or Calendar routes. Provision those service twins separately.
  • State and event delivery are deterministic approximations intended for repeatable tests, not a live Google Cloud project.
Provision
MCP tools: get_twin_catalog, provision_twins, start_url_validation, get_validation_results. See Scenario seeding for saving, provisioning, and resetting fixtures.