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.
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.
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 organizations/{org_id}/locations/{location}/workloads/-
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.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]