Assured Workloads Basics
GoogleOfficialPublished by Google
- Skill
- Tool integration
- Cloud and DevOps
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
This skill provides a structured workflow for managing Google Cloud Assured Workloads V1. It enables users to provision, inspect, update, and delete compliant folders and workloads across various regimes such as FedRAMP, DoD, and regional data boundaries. The skill emphasizes strict adherence to parameter validation, mandatory telemetry attribution, and human-in-the-loop confirmation for all mutating operations to ensure compliance and operational safety.
What it does
- Provisions new Assured Workloads V1 compliant folders and workloads.
- Lists and describes existing workloads for audit and inspection.
- Updates workload metadata and manages compliance posture updates.
- Safely deletes workloads by enforcing a strict bottom-up resource removal sequence.
- Configures service usage restrictions and CMEK settings for compliance.
- Diagnoses common API errors and LRO failures during workload operations.
When to use it
- When creating a new compliant workload environment in Google Cloud.
- When you need to audit or list existing Assured Workloads configurations.
- When updating workload labels or violation notification settings.
- When decommissioning a compliant workload and its associated resources.
- When applying available compliance posture updates to existing workloads.
Advantages
- Ensures consistent application of compliance regimes and data boundaries.
- Prevents accidental misconfiguration through mandatory parameter validation.
- Provides a safe, ordered sequence for deleting complex workload resources.
- Automates the complex process of applying compliance posture updates.
- Includes built-in diagnostic tools for troubleshooting API errors.
Usage examples
- “Create a new FedRAMP Moderate workload in the us-east1 region.”
- The agent will validate the parameters, request confirmation, and execute the gcloud command to provision the workload with the correct compliance regime.
- “List all Assured Workloads in my organization.”
- The agent will retrieve and display a JSON list of all workloads, including their current status and compliance details.
- “Delete the Assured Workload with ID 12345.”
- The agent will inspect the workload, identify child resources, and guide the user through the required bottom-up deletion process.
- “Check for and apply any pending compliance updates for my workload.”
- The agent will query the updates API, identify available changes, and apply them sequentially after user approval.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/google/assured-workloads-basics/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip assured-workloads-basics.zip -d .agents/skills
Documentation by Google
Google Cloud Assured Workloads Basics (V1 GA)
Validate prerequisites, create Assured Workloads V1 compliant folders, allowlist compliant services, and list, inspect, update, or delete existing workloads using gcloud and the Google Cloud Python Client Libraries (google-cloud-assured-workloads and google-api-python-client).
Usage Attribution
For all gcloud CLI, REST API, and MCP attribution requirements when executing commands with this skill, follow the instructions in Usage Attribution.
Mandatory Guardrails
No Fabrication: Never invent Organization IDs, Billing Account IDs, Folder IDs, Project IDs, Workload IDs, or Compliance Regime enums. Validate parameters with
scripts/validate_params.pybefore running commands.Regional / Multi-Regional Locations & CLI Surface: Assured Workloads V1 does not support
--location=global; always use a regional or multi-regional location compatible with the compliance regime (see references/regimes.md). Never usegcloud compliance-managercommands for Assured Workloads V1 workloads.Human Confirmation Before Mutation: Read-only operations (
list,describe, andscripts/manage_workload_updates.py --action=list) can run immediately after validation, but you must obtain explicit user confirmation before executing any mutating or destructive command (create,restrict_allowed_resources.py,update,manage_workload_updates.py --action=apply,delete,folders delete, orprojects delete).Telemetry Attribution & Regional Endpoints:
Prefix every
gcloudcommand you execute directly withCLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:assured-workloads-basics)"(see Usage Attribution).Configure Python GAPIC and Discovery clients with regional
ClientOptions(api_endpoint="{location}-assuredworkloads.googleapis.com").
Step 0: Prerequisites & Environment Setup
Verify these 5 prerequisites before running Assured Workloads operations:
CLI & Python Libraries: Install the Google Cloud SDK (
gcloud— see the Google Cloud SDK Installation Guide) and Python client libraries:pip install "google-cloud-assured-workloads>=1.0,<2" "google-api-python-client>=2.0,<3" "google-auth>=2.0,<3"Dual Authentication (CLI + ADC): Authenticate both
gcloudand Application Default Credentials (gcloud auth login && gcloud auth application-default login, orgcloud auth activate-service-account --key-file=/path/to/key.json+export GOOGLE_APPLICATION_CREDENTIALS="/path/to/key.json").Quota & Admin Project:
gcloud config set project {admin_project_id}andgcloud auth application-default set-quota-project {admin_project_id}.API Enablement: Enable the Assured Workloads API (
assuredworkloads.googleapis.com):gcloud services enable assuredworkloads.googleapis.com --project={admin_project_id}Organization-Level IAM Roles (
organizations/{org_id}):Caller:
roles/assuredworkloads.admin(orroles/assuredworkloads.reader/roles/assuredworkloads.editorfor read-onlylist/describe),roles/resourcemanager.organizationViewer, androles/billing.useron--billing-account=billingAccounts/{billing_id}when creating workloads (plusbilling.resourceAssociations.createon--partner-services-billing-accountfor partner workloads).Assured Workloads Service Agent (
service-{org_number}@gcp-sa-assuredworkloads.iam.gserviceaccount.com):roles/assuredworkloads.serviceAgent.
Workflow 1: Create an Assured Workloads workload (Two-Phase Provisioning)
Phase 1: Validate Parameters & Create Workload (gcloud assured workloads create)
Select Regime & Location: Check references/regimes.md for all 45 V1
--compliance-regimeenums and valid--locationvalues.Free-Tier Regional Data Boundaries (
REGIONAL_DATA_BOUNDARY): Free-tier regional data boundaries (e.g., US Data Boundary with standard commercial support and without sovereign personnel support uplift, EU Data Boundary, Australia/India/UK/Canada/Israel Data Boundary) map to--compliance-regime=REGIONAL_DATA_BOUNDARY(legacy alias:REGIONAL_CONTROLS) paired with--location={location}(except Japan, which usesJAPAN_DATA_BOUNDARY). Do not set--compliance-regimeto paid sovereign support regimes (US_REGIONS_AND_US_SUPPORT,US_DATA_BOUNDARY_AND_SUPPORT,FEDRAMP_MODERATE) when the user requests the free-tier boundary, and never invent non-existent enums likeUS_DATA_BOUNDARY.
Billing Account Discovery (If Omitted): Never guess a billing account ID. If omitted, run
gcloud billing accounts list --filter="open=true" --format="table(name,displayName)"or ask the user forbillingAccounts/{billing_id}.Validate & Create: Validate with
python3 scripts/validate_params.py --operation=create ..., surface any warnings, obtain explicit user confirmation, and executegcloud assured workloads create:gcloud assured workloads create \ --organization={org_id} --location={location} \ --display-name="{display_name}" --compliance-regime={compliance_regime} \ --billing-account=billingAccounts/{billing_id} \ [--provisioned-resources-parent=folders/{parent_folder_id}] [--enable-sovereign-controls] \ [--next-rotation-time={next_rotation_time} --rotation-period={rotation_seconds}s] \ [--resource-settings=consumer-project-id={consumer_project_id},consumer-project-name={consumer_project_name},encryption-keys-project-id={kms_project_id},encryption-keys-project-name={kms_project_name},keyring-id={keyring_id}] \ [--partner={partner_enum}] [--partner-permissions=data-logs-viewer=true|false] \ [--partner-services-billing-account=billingAccounts/{partner_billing_id}] \ [--labels=key1=val1,key2=val2] [--external-identifier={external_id}] --format=jsonCMEK & Resource Settings Rules:
--next-rotation-time(RFC 3339 timestamp) and--rotation-period(seconds, e.g.172800s) must be specified together.encryption-keys-project-id,encryption-keys-project-name, andkeyring-idin--resource-settingsrequire both rotation flags.Sovereign Controls by Partners (
--compliance-regime=ASSURED_WORKLOADS_FOR_PARTNERS):Requests for partner-managed sovereign controls (S3NS, T-Systems, SIA Minsait, PSN, CNTXT, Telefónica) map to
--compliance-regime=ASSURED_WORKLOADS_FOR_PARTNERS.Requires
--partnerand a supported partner region (see references/regimes.md for valid--partnervalues, supported regions, and partner billing account requirements).Configure partner permissions on the CLI with
--partner-permissions=data-logs-viewer=true(ordata-logs-viewer=false).
Phase 2 (Optional): Allowlist Compliant Services / Enable BigQuery (google-cloud-assured-workloads)
When Required: For
FEDRAMP_MODERATEandDATA_BOUNDARY_FOR_FEDRAMP_MODERATE, BigQuery is automatically enabled at creation (skip Phase 2). For all other regimes (such asFEDRAMP_HIGH), BigQuery is initially blocked by the folder'sconstraints/gcp.restrictServiceUsageorganization policy while a background configuration process completes (typically 5–10 minutes after creation).Never Bypass Org Policies Manually: Do not manually override or delete
constraints/gcp.restrictServiceUsageon the folder to bypass Assured Workloads compliance controls.Programmatic Allowlisting (
AssuredWorkloadsServiceClient.restrict_allowed_resources): Once background setup completes and compliant services (like BigQuery) appear incompliantButDisallowedServices, runpython3 scripts/restrict_allowed_resources.py --organization={org_id} --location={location} --workload-id={workload_id} --restriction-type=ALLOW_COMPLIANT_RESOURCES(after user confirmation), or call the officialgoogle-cloud-assured-workloadsPython client library directly:from google.api_core.client_options import ClientOptions from google.cloud import assuredworkloads_v1 client = assuredworkloads_v1.AssuredWorkloadsServiceClient( client_options=ClientOptions( api_endpoint=f"{location}-assuredworkloads.googleapis.com" ), transport="rest", ) request = assuredworkloads_v1.RestrictAllowedResourcesRequest( name=f"organizations/{org_id}/locations/{location}/workloads/{workload_id}", restriction_type=assuredworkloads_v1.RestrictAllowedResourcesRequest.RestrictionType.ALLOW_COMPLIANT_RESOURCES, ) client.restrict_allowed_resources(request=request)(Supported
RestrictionTypevalues:ALLOW_COMPLIANT_RESOURCES,APPEND_COMPLIANT_RESOURCES, orALLOW_ALL_GCP_RESOURCES).
Workflow 2: List & Describe Assured Workloads workloads (gcloud)
Read-only list and describe operations do not require user confirmation after validating with scripts/validate_params.py.
List Workloads (
ListWorkloads):gcloud assured workloads list --organization={org_id} --location={location} \ [--filter="{filter_expression}"] [--limit={limit}] [--page-size={page_size}] --format=jsonDescribe a Specific Workload (
GetWorkload):gcloud assured workloads describe {workload_id} --organization={org_id} --location={location} --format=json(Or pass the full resource name
organizations/{org_id}/locations/{location}/workloads/{workload_id}).Key
describeOutput Fields:name,displayName,complianceRegime,partner,resources(provisionedCONSUMER_FOLDERfolder ID,CONSUMER_PROJECT,ENCRYPTION_KEYS_PROJECT, andKEYRING),etag(optimistic concurrency token required forupdate/delete),compliantButDisallowedServices,kajEnrollmentState,saaEnrollmentResponse,violationNotificationsEnabled, andlabels.
Workflow 3: Delete an Assured Workloads workload (DeleteWorkload)
An Assured Workloads workload cannot be deleted while its provisioned Cloud Resource Manager folder (folders/{folder_id}) or child projects still exist (FAILED_PRECONDITION: Workload is not empty / ERROR_CODE_WORKLOAD_NOT_EMPTY). Never run gcloud assured workloads delete before deleting the provisioned folder and its child projects.
Inspect & Validate: Run
gcloud assured workloads describeto identify the provisioned folder (folders/{folder_id}) and child projects ({project_id}), and validate withpython3 scripts/validate_params.py --operation=delete --workload-id={workload_id} --organization={org_id} --location={location}.Confirm & Execute Ordered Deletion Sequence: Obtain explicit user confirmation, then run in strict bottom-up order:
# Step 1: Delete child projects inside the workload folder first gcloud projects delete {project_id} --quiet # Step 2: Delete the provisioned Assured Workloads folder gcloud resource-manager folders delete {folder_id} # Step 3: Delete the Assured Workloads workload after folder deletion propagates gcloud assured workloads delete {workload_id} --organization={org_id} --location={location} --quietPropagation Delay &
--etagNote: Folder deletion state (DELETE_REQUESTED) can take a brief propagation delay (15–60s) before Assured Workloads recognizes the folder as deleted. IfERROR_CODE_WORKLOAD_NOT_EMPTYtransiently persists after deleting the folder, wait 15–20 seconds and retrygcloud assured workloads deletewithout a stale--etag(as deleting underlying resources changes the workload's concurrency token).
Workflow 4: Update an Assured Workloads workload (UpdateWorkload & Compliance Updates)
4A. Update Workload Metadata & Notifications (gcloud assured workloads update)
Updatable Fields (at least one required):
--display-name="{new_display_name}": 4–30 characters ([a-zA-Z0-9 -], no trailing spaces).--labels=key1=val1,key2=val2: Replaces the workload's label map (include existing labels to preserve them).--violation-notifications-enabled=true|false: Enables or disables email notifications for organization policy compliance violations to Essential Contacts (Legal category).--etag={etag}: Current concurrency token fromdescribe/list.
Immutable Fields (Cannot Be Modified After Creation):
complianceRegime,location,billingAccount, andpartnerare immutable.gcloud assured workloads updatecannot change a workload'scomplianceRegimeorlocationin-place; changing regimes requires creating a new Assured Workloads workload.Validate, Confirm, & Execute: Validate with
python3 scripts/validate_params.py --operation=update ..., obtain explicit user confirmation, and run:gcloud assured workloads update {workload_id} --organization={org_id} --location={location} \ [--display-name="{new_display_name}"] [--labels=key1=val1,key2=val2] \ [--violation-notifications-enabled=true|false] [--etag={etag}] --format=json
4B. List & Apply Compliance Posture Updates (updates.list & updates.apply)
gcloud assured workloads does not have a built-in CLI subcommand to list or apply compliance posture updates from the updates sub-resource (gcloud assured workloads update only updates workload metadata). Use scripts/manage_workload_updates.py (--action=list or --action=apply after user confirmation) or googleapiclient.discovery.build against the regional Assured Workloads v1 API (https://{location}-assuredworkloads.googleapis.com):
AVAILABLEvs.WITHDRAWNUpdate States:AVAILABLE(One Update Per Constraint): EachAVAILABLEupdate record corresponds to an individual organization policy constraint update (details.orgPolicyUpdate.suggestedPolicy.constraint). If multiple updates areAVAILABLE, each corresponds to a different constraint and must be applied individually (or sequentially via--update-id=ALL)—applying the newest update does not apply olderAVAILABLEupdates for other constraints.WITHDRAWN(Superseded): When a newer policy update supersedes an older unapplied update for the same constraint, Assured Workloads marks the older updateWITHDRAWN. Filter for stateAVAILABLEand never applyWITHDRAWNupdates.
Python Discovery API Pattern (
updates.list,updates.apply, & LRO Polling):import time from google.api_core.client_options import ClientOptions from googleapiclient import discovery service = discovery.build( "assuredworkloads", "v1", client_options=ClientOptions( api_endpoint=f"https://{location}-assuredworkloads.googleapis.com" ), ) parent = f"organizations/{org_id}/locations/{location}/workloads/{workload_id}" # 1. List updates and filter for AVAILABLE state resp = ( service.organizations() .locations() .workloads() .updates() .list(parent=parent) .execute() ) available = [u for u in resp.get("updates", []) if u.get("state") == "AVAILABLE"] # 2. Apply each AVAILABLE update and poll the returned Long-Running Operation (LRO) for update in available: op = ( service.organizations() .locations() .workloads() .updates() .apply(name=update["name"], body={}) .execute() ) while not op.get("done", False): time.sleep(3) op = ( service.organizations() .locations() .operations() .get(name=op["name"]) .execute() )
Common Error Handling & Troubleshooting (scripts/diagnose_error.py)
Never blindly retry deterministic 400 INVALID_ARGUMENT, 403 PERMISSION_DENIED, 404 NOT_FOUND, or FAILED_PRECONDITION errors. Run python3 scripts/diagnose_error.py --error-message="{error_output_text}" to match any error against the full Assured Workloads ErrorInfo.reason catalog.
Troubleshooting Folder creation was unsuccessful. Please try again. (LRO Inspection)
When gcloud assured workloads create fails with the generic message Folder creation was unsuccessful. Please try again., do not blindly retry. Inspect the failed Long-Running Operation (LRO) in the same organization and location to retrieve the specific ErrorInfo.reason:
gcloud assured operations list --organization={org_id} --location={location} --format=json
gcloud assured operations describe {operation_id} --organization={org_id} --location={location} --format=json(Or run python3 scripts/diagnose_error.py --fetch-latest-lro --organization={org_id} --location={location}).
Common Folder Creation Preconditions to Check in the LRO Error:
Duplicate sibling folder display name (
ERROR_CODE_FOLDER_NAME_UNIQUENESS): A sibling folder with the same--display-namealready exists under the target parent (organizations/{org_id}orfolders/{parent_folder_id}). Choose a unique--display-nameor a different--provisioned-resources-parent.Nesting inside an existing Assured Workloads folder (
ERROR_CODE_INVALID_PROVISIONED_RESOURCES_PARENT): Assured Workloads folders cannot be nested inside another Assured Workloads folder. Specify a standard non-workload parent folder or omit--provisioned-resources-parent.Folder quota or nesting depth limit (
ERROR_CODE_FOLDER_CREATION_PRECONDITION_FAILED): The target parent reached the Cloud Resource Manager 300 direct child-folder quota or the 10-level folder nesting depth limit.
Reference Documentation
references/regimes.md: Complete table of all 45 Assured Workloads V1 compliance regimes, modern
DATA_BOUNDARY_FOR_*enums, legacy aliases, partner enums, and supported regional/multi-regional locations.Official Google Cloud Documentation: Assured Workloads Overview, Supported Locations & Data Boundaries, Assured Workloads Pricing, Apply Workload Updates, Sovereign Controls by Partners Overview, Sovereign Controls by Partners Locations.
Files
- ATTRIBUTION.mdAdded by AutoGineer866 B
- LICENSELicence file added by AutoGineer11.1 KiB
- SKILL.md19.0 KiB
- references/attribution.md1.8 KiB
- references/regimes.md13.7 KiB
- scripts/diagnose_error.pyScript16.4 KiB
- scripts/manage_workload_updates.pyScript26.1 KiB
- scripts/restrict_allowed_resources.pyScript13.8 KiB
- scripts/validate_params.pyScript56.2 KiB
scripts/diagnose_error.py
#!/usr/bin/env python3
r"""Common error handler and LRO failure diagnostics for Assured Workloads V1.
Parses CLI / API error messages or inspects the latest failed Long-Running
Operation (LRO) in an organization and location (`operations.list` /
`operations.get`) to map public `google.rpc.ErrorInfo.reason` codes (`ERROR_CODE_*`)
to deterministic root causes and remediation steps across Create, List/Describe,
Update, and Delete workflows.
Usage examples:
# Diagnose a CLI or API error message directly:
python3 scripts/diagnose_error.py \
--error-message="FAILED_PRECONDITION: ... ERROR_CODE_WORKLOAD_NOT_EMPTY"
# Inspect the latest failed LRO when `gcloud assured workloads create` prints
# "ERROR: (gcloud.assured.workloads.create) Folder creation was unsuccessful. Please try again.":
python3 scripts/diagnose_error.py \
--fetch-latest-lro \
--organization=123456789012 \
--location=us-central1
"""
import argparse
import json
import re
import sys
from typing import Any
USER_AGENT = "agent-skills/1.0 (skill:assured-workloads-basics)"
_ORG_ID_RE = re.compile(r"^\d+$")
_ERROR_CODE_RE = re.compile(r"\b(ERROR_CODE_[A-Z0-9_]+)\b")
_AXT_ERROR_ENTRY: dict[str, Any] = {
"workflow": "create",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"Access Transparency is not enabled (or was disabled) on the"
" Organization, which is required for this compliance regime or"
" '--enable-sovereign-controls'."
),
"remediation": (
"Enable Access Transparency for the Google Cloud Organization in"
" the Cloud Console (or contact Google Cloud Support if it was"
" previously disabled) before creating the workload."
),
}
ERROR_CATALOG: dict[str, dict[str, Any]] = {
"ERROR_CODE_FOLDER_CREATION_PRECONDITION_FAILED": {
"workflow": "create",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"The target parent ('organizations/<ORG_ID>' or"
" 'folders/<PARENT_FOLDER_ID>') reached the Cloud Resource Manager"
" 300 direct child-folder quota or the 10-level folder nesting"
" depth limit."
),
"remediation": (
"Pass '--provisioned-resources-parent=folders/<FOLDER_ID>' pointing"
" to an existing non-workload parent folder with available"
" child-folder capacity."
),
},
"ERROR_CODE_FOLDER_NAME_UNIQUENESS": {
"workflow": "create",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"A sibling folder with the same '--display-name' already exists"
" directly under the target parent."
),
"remediation": (
"Choose a unique '--display-name' or specify a different"
" '--provisioned-resources-parent=folders/<FOLDER_ID>'."
),
},
"ERROR_CODE_INVALID_PROVISIONED_RESOURCES_PARENT": {
"workflow": "create",
"canonicalStatus": "INVALID_ARGUMENT",
"retryable": False,
"rootCause": (
"The specified '--provisioned-resources-parent' folder is itself"
" already an Assured Workloads folder (Assured Workloads"
" environments cannot be nested inside another Assured Workloads"
" folder)."
),
"remediation": (
"Select a standard non-workload folder for"
" '--provisioned-resources-parent' or omit the flag to provision"
" under the organization root."
),
},
"ERROR_CODE_PROJECT_ID_ALREADY_IN_USE": {
"workflow": "create",
"canonicalStatus": "INVALID_ARGUMENT",
"retryable": False,
"rootCause": (
"The custom 'consumer-project-id' or 'encryption-keys-project-id'"
" specified in '--resource-settings' is already in use globally."
),
"remediation": (
"Choose a globally unique project ID in '--resource-settings'."
),
},
"ERROR_CODE_PROJECT_DISPLAY_NAME_EXCEEDS_LIMIT": {
"workflow": "create",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"The custom project display name ('consumer-project-name' or"
" 'encryption-keys-project-name') exceeds 30 characters."
),
"remediation": (
"Shorten custom project display names in '--resource-settings' to"
" 30 characters or fewer."
),
},
"ERROR_CODE_WORKLOAD_NOT_EMPTY": {
"workflow": "delete",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": True,
"rootCause": (
"Assured Workloads workload deletion requires all provisioned"
" Cloud Resource Manager projects ('ENCRYPTION_KEYS_PROJECT',"
" 'CONSUMER_PROJECT') and the workload folder ('CONSUMER_FOLDER')"
" to be deleted first, or folder deletion status"
" ('DELETE_REQUESTED') is still propagating (15-60 seconds)."
),
"remediation": (
"Case A (Underlying folder/projects still active): Obtain explicit"
" user confirmation, delete any projects inside the folder first"
" ('gcloud projects delete <PROJECT_ID> --quiet'), then delete the"
" workload folder ('gcloud resource-manager folders delete"
" <FOLDER_ID>'). Case B (Folder was deleted within the last 60"
" seconds): Wait 15-20 seconds for Cloud Resource Manager folder"
" deletion status to propagate and retry 'gcloud assured workloads"
" delete' (up to 3 times over 60s, omitting '--etag')."
),
},
"ERROR_CODE_COMPLIANCE_UPDATE_NOT_ENABLED": {
"workflow": "update",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"Compliance configuration updates are not yet enabled on this"
" older Assured Workloads folder."
),
"remediation": (
"Re-run 'python3 scripts/manage_workload_updates.py --action=list"
" --enable-compliance-updates' (or '--action=enable'). Ensure the"
" caller holds 'roles/resourcemanager.folderIamAdmin' on the"
" folder."
),
},
"ERROR_CODE_WORKLOAD_UPDATE_NOT_APPLICABLE": {
"workflow": "update",
"canonicalStatus": "FAILED_PRECONDITION",
"retryable": False,
"rootCause": (
"The organization policy on the workload folder was manually"
" modified after the workload update became available."
),
"remediation": (
"Compare the folder's current organization policy with"
" 'details.orgPolicyUpdate.appliedPolicy', restore the previous"
" organization policy setting on the folder (or wait for the next"
" periodic update evaluation), and re-run '--action=list'."
),
},
"ERROR_CODE_PERMISSION_DENIED": {
"workflow": "all",
"canonicalStatus": "PERMISSION_DENIED",
"retryable": False,
"rootCause": (
"The caller or the Assured Workloads Service Agent is missing"
" required IAM permissions."
),
"remediation": (
"Check 'metadata.missing_permissions' in the error output. Verify"
" the caller holds 'roles/assuredworkloads.admin' on"
" 'organizations/<ORG_ID>' (plus 'roles/billing.user' on the"
" billing account when creating workloads) and that"
" 'service-<ORG_NUMBER>@gcp-sa-assuredworkloads.iam.gserviceaccount.com'"
" holds 'roles/assuredworkloads.serviceAgent'."
),
},
"ERROR_CODE_BILLING_ACCOUNT_INVALID": {
"workflow": "create",
"canonicalStatus": "INVALID_ARGUMENT",
"retryable": False,
"rootCause": (
"The specified '--billing-account' (or"
" '--partner-services-billing-account') is invalid, closed, or the"
" caller lacks permissions to associate it."
),
"remediation": (
"Run 'gcloud billing accounts list --filter=\"open=true\"' to"
" select an active billing account and verify the caller holds"
" 'roles/billing.user' (and 'billing.resourceAssociations.create'"
" for partner billing accounts)."
),
},
"ERROR_CODE_BILLING_QUOTA_EXCEEDED": {
"workflow": "create",
"canonicalStatus": "RESOURCE_EXHAUSTED",
"retryable": False,
"rootCause": (
"The billing account has reached its maximum linked project quota."
),
"remediation": (
"Select a different open billing account or request a billing"
" account project quota increase."
),
},
"ERROR_CODE_ACCESS_TRANSPARENCY_NOT_ENABLED": _AXT_ERROR_ENTRY,
"ERROR_CODE_ACCESS_TRANSPARENCY_DISABLED": _AXT_ERROR_ENTRY,
}
def _create_discovery_service(location: str) -> Any:
"""Creates a regional Assured Workloads v1 Discovery service with telemetry."""
try:
import google.auth # pylint: disable=g-import-not-at-top
from google.api_core.client_options import ClientOptions # pylint: disable=g-import-not-at-top
from googleapiclient import discovery # pylint: disable=g-import-not-at-top
import googleapiclient.http # pylint: disable=g-import-not-at-top
except ImportError as exc:
raise RuntimeError(
"Missing required Python packages 'google-api-python-client' and"
" 'google-auth'. Install via: pip install"
' "google-api-python-client>=2.0,<3" "google-auth>=2.0,<3"'
) from exc
credentials, _ = google.auth.default()
endpoint = f"https://{location}-assuredworkloads.googleapis.com"
service = discovery.build(
"assuredworkloads",
"v1",
credentials=credentials,
client_options=ClientOptions(api_endpoint=endpoint),
)
if hasattr(service, "_http") and hasattr(
googleapiclient.http, "set_user_agent"
):
googleapiclient.http.set_user_agent(service._http, USER_AGENT)
return service
def fetch_latest_failed_lro(
organization: str,
location: str,
limit: int = 5,
service: Any = None,
) -> dict[str, Any] | None:
"""Fetches the most recent failed LRO in organizations/<ORG>/locations/<LOC>."""
clean_org = organization.strip()
if clean_org.startswith("organizations/"):
clean_org = clean_org[len("organizations/") :].strip()
if not _ORG_ID_RE.fullmatch(clean_org):
raise ValueError(
f"Invalid organization ID '{organization}'. Expected numeric ID."
)
clean_loc = location.strip().lower()
if not clean_loc or clean_loc == "global":
raise ValueError(
f"Invalid location '{location}'. Assured Workloads V1 requires a"
" regional or multi-regional location."
)
if service is None:
service = _create_discovery_service(clean_loc)
parent = f"organizations/{clean_org}/locations/{clean_loc}"
ops_resource = service.organizations().locations().operations()
response = ops_resource.list(name=parent, pageSize=limit).execute() or {}
operations = response.get("operations", [])
for op in operations:
if "error" in op:
return op
return None
def diagnose_error(
error_message: str | None = None,
fetch_latest_lro: bool = False,
organization: str | None = None,
location: str | None = None,
service: Any = None,
) -> dict[str, Any]:
"""Diagnoses an Assured Workloads CLI/API error or failed LRO."""
if not error_message and not fetch_latest_lro:
raise ValueError(
"Provide '--error-message' and/or '--fetch-latest-lro' (with"
" '--organization' and '--location')."
)
failed_lro: dict[str, Any] | None = None
combined_text = error_message or ""
if fetch_latest_lro:
if not organization or not location:
raise ValueError(
"'--organization' and '--location' are required when"
" '--fetch-latest-lro' is set."
)
failed_lro = fetch_latest_failed_lro(
organization=organization,
location=location,
service=service,
)
if failed_lro:
combined_text = f"{combined_text}\n{json.dumps(failed_lro)}"
matched_codes: list[str] = []
for match in _ERROR_CODE_RE.finditer(combined_text):
code = match.group(1)
if code not in matched_codes:
matched_codes.append(code)
if (
not matched_codes
and "Folder creation was unsuccessful. Please try again." in combined_text
and not fetch_latest_lro
):
return {
"status": "NEEDS_LRO_INSPECTION",
"retryable": False,
"rootCause": (
"gcloud assured workloads create returned a generic folder creation"
" error. The underlying reason is recorded on the Long-Running"
" Operation (LRO)."
),
"remediation": (
"Do not blindly retry 'gcloud assured workloads create'. Re-run"
" 'python3 scripts/diagnose_error.py --fetch-latest-lro"
" --organization=<ORG_ID> --location=<LOCATION>' (or run 'gcloud"
" assured operations list --organization=<ORG_ID>"
" --location=<LOCATION> --limit=5 --format=json') to inspect the"
" LRO error code."
),
}
diagnoses: list[dict[str, Any]] = []
for code in matched_codes:
if code in ERROR_CATALOG:
entry = dict(ERROR_CATALOG[code])
entry["errorCode"] = code
diagnoses.append(entry)
else:
diagnoses.append({
"errorCode": code,
"workflow": "unknown",
"canonicalStatus": "UNKNOWN",
"retryable": False,
"rootCause": f"Assured Workloads returned error code '{code}'.",
"remediation": (
"Inspect the full error details and verify input parameters, IAM"
" roles, and resource preconditions before retrying."
),
})
if not diagnoses:
return {
"status": "UNRECOGNIZED_ERROR",
"retryable": False,
"matchedErrorCodes": [],
"failedOperation": failed_lro.get("name") if failed_lro else None,
"rootCause": (
"No specific Assured Workloads ERROR_CODE_* token was found in the"
" error output."
),
"remediation": (
"Do not blindly retry deterministic 400/403/404 errors. Verify"
" parameters with 'scripts/validate_params.py' and check IAM roles"
" in Step 0."
),
}
primary = diagnoses[0]
result: dict[str, Any] = {
"status": "DIAGNOSED",
"primaryErrorCode": primary["errorCode"],
"workflow": primary["workflow"],
"canonicalStatus": primary["canonicalStatus"],
"retryable": primary["retryable"],
"rootCause": primary["rootCause"],
"remediation": primary["remediation"],
"matchedErrorCodes": matched_codes,
"diagnoses": diagnoses,
}
if failed_lro:
result["failedOperationName"] = failed_lro.get("name")
result["failedOperationError"] = failed_lro.get("error")
return result
def build_arg_parser() -> argparse.ArgumentParser:
parser = argparse.ArgumentParser(
description=(
"Diagnose Assured Workloads V1 CLI/API errors and failed"
" Long-Running Operations."
)
)
parser.add_argument(
"--error-message",
default=None,
help="Raw error string or JSON output from gcloud or Python script.",
)
parser.add_argument(
"--fetch-latest-lro",
action="store_true",
help=(
"Query the Assured Workloads operations.list API to inspect the most"
" recent failed LRO in --organization and --location."
),
)
parser.add_argument(
"--organization",
default=None,
help="Numeric Organization ID (required when --fetch-latest-lro is set).",
)
parser.add_argument(
"--location",
default=None,
help=(
"Regional or multi-regional location (required when"
" --fetch-latest-lro is set)."
),
)
return parser
def main(argv: list[str] | None = None) -> int:
parser = build_arg_parser()
args = parser.parse_args(argv)
try:
result = diagnose_error(
error_message=args.error_message,
fetch_latest_lro=args.fetch_latest_lro,
organization=args.organization,
location=args.location,
)
print(json.dumps(result, indent=2))
return 0
except (ValueError, RuntimeError) as err:
sys.stderr.write(f"DIAGNOSE_ERROR_FAILURE: {err}\n")
return 1
if __name__ == "__main__":
sys.exit(main())
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs a command-line tool, Needs Python
Security
What our scanner noticed· Low risk
- Instructions that use the network
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Publisher
- Google (Official)
- Source
- google/skills · skills/cloud/assured-workloads-basics · commit 2194d3b
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Google or Google.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download assured-workloads-basics.zip