google_drive in twins and put this configuration under seed_config.google_drive.
Google Drive with folders and files.
Example seed
This is the complete Scenario request body for creating a Scenario. You can also import it witharga test-runner scenarios import --file scenario.json.
Parameters
The following fields belong directly insideseed_config.google_drive. Required nested fields are marked in their tables. Provider-native objects can contain service-specific fields beyond the representative record shapes below.
Seeding behavior
Drive, Docs, and Sheets remain independently provisioned APIs. When selected in the same Twin Run, they share run-scoped file state. Sibling seeds must agree on OAuth configuration, principals, tokens, assistant settings, and any explicitbase_time.
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.folders[]
folders[].files[]
Typed configuration objects
Named object types in the parameter table use these fields.ConnectedSheetsConfig
DataSourceResult
DocsGeminiConfig
GeminiResponse
SeedPrincipal
SeedToken
SheetsGeminiConfig
SheetsGeminiResponse
SheetsGeminiAction
API coverage and limitations
Twin name:google_drive
CLI quickstart: Use the Google Workspace CLI with Arga twins
Supports
- Google Drive API v3 files, permissions, revisions, comments, replies, shared drives, changes, watch channels, and simple, multipart, and resumable uploads.
- File operations such as list, get, create, update, copy, delete, export, download, labels, permissions, and generated IDs.
- Preset metadata for
google-docs-launch-notesandgoogle-sheets-launch-plan, matching the default resource IDs in the separately provisioned editor twins. - Google API client compatibility through a Drive discovery document.
- Authorization-code OAuth, S256 PKCE, offline refresh, and signed OIDC ID tokens. See Google OAuth and OIDC setup for callback registration and token verification.
- OAuth scope enforcement, change polling, watch notifications, deterministic retries, replay, and storage tier-based quotas.
- The Drive
qquery language andorderBysupport are intentionally a subset; unsupported clauses or keys return400 invalidQuery. - Unsupported export formats return
400 cannotExportFile; Google-native exports focus on common document, sheet, slide, form, script, site, and drawing formats. - HMAC notification signatures are a twin-only optional approximation and are disabled by default.
- Upload MIME types are accepted broadly, but preview, thumbnail, edit, export, and search capabilities depend on the modeled MIME class.
- The Google Docs and Google Sheets editor twins are not part of this provision. Request
google_docsandgoogle_sheetsseparately for their APIs and UIs. People, Workspace Events, Apps Script, and Pub/Sub are undergoogle_workspace.
get_twin_catalog, provision_twins, start_url_validation, get_validation_results.
See Scenario seeding for saving, provisioning, and resetting fixtures.
