Reference documentation and code samples for the Assured Workloads v1 API enum Violation.Types.Remediation.Types.RemediationType.
Classifying remediation into various types based on the kind of
violation. For example, violations caused due to changes in boolean org
policy requires different remediation instructions compared to violation
caused due to changes in allowed values of list org policy.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe latest version of the Assured Workloads v1 API documentation is 2.6.0, and the page provides links to previous versions, ranging back to 1.0.0.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eRemediationType\u003c/code\u003e enum is used to categorize different types of remediations for violations, such as those arising from boolean or list organization policy changes.\u003c/p\u003e\n"],["\u003cp\u003eThere are specific \u003ccode\u003eRemediationType\u003c/code\u003e fields for different violation types, including boolean org policies, list org policies with allowed or denied values, and \u003ccode\u003egcp.restrictCmekCryptoKeyProjects\u003c/code\u003e policies.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eUnspecified\u003c/code\u003e field is a catch-all for remediation types that don't fall into the other specific categories.\u003c/p\u003e\n"]]],[],null,[]]
