A base abstract class for Assuredworkloads requests.
The Assuredworkloads Service.
Available OAuth 2.0 scopes for use with the Assured Workloads API.
Available OAuth 2.0 scope constants for use with the Assured Workloads API.
The "organizations" collection of methods.
The "locations" collection of methods.
The "operations" collection of methods.
Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.
Lists operations that match the specified filter in the request. If the server doesn't support this
method, it returns
The "workloads" collection of methods.
Analyzes a hypothetical move of a source resource to a target workload to surface compliance risks. The analysis is best effort and is not guaranteed to be exhaustive.
Creates Assured Workload.
Deletes the workload. Make sure that workload's direct children are already in a deleted state, otherwise the request will fail with a FAILED_PRECONDITION error. In addition to assuredworkloads.workload.delete permission, the user should also have orgpolicy.policy.set permission on the deleted folder to remove Assured Workloads OrgPolicies.
Enable resource violation monitoring for a workload.
Gets Assured Workload associated with a CRM Node
Lists Assured Workloads under a CRM Node.
Update the permissions settings for an existing partner workload. For force updates don't set etag field in the Workload. Only one update operation per workload can be in progress.
Updates an existing workload. Currently allows updating of workload display_name and labels. For force updates don't set etag field in the Workload. Only one update operation per workload can be in progress.
Restrict the list of resources allowed in the Workload environment. The current list of allowed products can be found at https://cloud.google.com/assured-workloads/docs/supported-products In addition to assuredworkloads.workload.update permission, the user should also have orgpolicy.policy.set permission on the folder resource to use this functionality.
The "violations" collection of methods.
Acknowledges an existing violation. By acknowledging a violation, users acknowledge the existence of a compliance violation in their workload and decide to ignore it due to a valid business justification. Acknowledgement is a permanent operation and it cannot be reverted.
Retrieves Assured Workload Violation based on ID.
Lists the Violations in the AssuredWorkload Environment. Callers may also choose to read across
multiple Workloads as per AIP-159 by using '-' (the hyphen or dash
character) as a wildcard character instead of workload-id in the parent. Format
Data format for response.
V1 error format.