From 2da03fb83a1bf6e0b5116f6e7d2b2ffdcfceece9 Mon Sep 17 00:00:00 2001
From: Yoshi Automation <yoshi-automation@google.com>
Date: Tue, 10 Dec 2024 07:09:38 +0000
Subject: [PATCH] feat(orgpolicy): update the api

#### orgpolicy:v2

The following keys were added:
- schemas.GoogleCloudOrgpolicyV2Constraint.properties.supportsSimulation.type (Total Keys: 1)
- schemas.GoogleCloudOrgpolicyV2PolicySpecPolicyRule.properties.parameters (Total Keys: 2)
---
 .../dyn/orgpolicy_v2.folders.constraints.html |  1 +
 docs/dyn/orgpolicy_v2.folders.policies.html   | 63 +++++++++++++++++++
 ...rgpolicy_v2.organizations.constraints.html |  1 +
 .../orgpolicy_v2.organizations.policies.html  | 63 +++++++++++++++++++
 .../orgpolicy_v2.projects.constraints.html    |  1 +
 docs/dyn/orgpolicy_v2.projects.policies.html  | 63 +++++++++++++++++++
 .../documents/orgpolicy.v2.json               | 14 ++++-
 7 files changed, 205 insertions(+), 1 deletion(-)

diff --git a/docs/dyn/orgpolicy_v2.folders.constraints.html b/docs/dyn/orgpolicy_v2.folders.constraints.html
index 30a8c023f6a..fdc8f8d6610 100644
--- a/docs/dyn/orgpolicy_v2.folders.constraints.html
+++ b/docs/dyn/orgpolicy_v2.folders.constraints.html
@@ -140,6 +140,7 @@ <h3>Method Details</h3>
       },
       &quot;name&quot;: &quot;A String&quot;, # Immutable. The resource name of the constraint. Must be in one of the following forms: * `projects/{project_number}/constraints/{constraint_name}` * `folders/{folder_id}/constraints/{constraint_name}` * `organizations/{organization_id}/constraints/{constraint_name}` For example, &quot;/projects/123/constraints/compute.disableSerialPortAccess&quot;.
       &quot;supportsDryRun&quot;: True or False, # Shows if dry run is supported for this constraint or not.
+      &quot;supportsSimulation&quot;: True or False, # Shows if simulation is supported for this constraint or not.
     },
   ],
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Page token used to retrieve the next page. This is currently not used.
diff --git a/docs/dyn/orgpolicy_v2.folders.policies.html b/docs/dyn/orgpolicy_v2.folders.policies.html
index 45a10b73b6f..9432cbdc653 100644
--- a/docs/dyn/orgpolicy_v2.folders.policies.html
+++ b/docs/dyn/orgpolicy_v2.folders.policies.html
@@ -131,6 +131,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -159,6 +162,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -188,6 +194,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -228,6 +237,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -256,6 +268,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -285,6 +300,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -351,6 +369,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -379,6 +400,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -408,6 +432,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -455,6 +482,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -483,6 +513,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -512,6 +545,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -564,6 +600,9 @@ <h3>Method Details</h3>
               },
               &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
               &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+              &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+                &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+              },
               &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
                 &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                   &quot;A String&quot;,
@@ -592,6 +631,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -621,6 +663,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -679,6 +724,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -707,6 +755,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -736,6 +787,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -777,6 +831,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -805,6 +862,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -834,6 +894,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
diff --git a/docs/dyn/orgpolicy_v2.organizations.constraints.html b/docs/dyn/orgpolicy_v2.organizations.constraints.html
index 1a06118eacb..14cea73e0e8 100644
--- a/docs/dyn/orgpolicy_v2.organizations.constraints.html
+++ b/docs/dyn/orgpolicy_v2.organizations.constraints.html
@@ -140,6 +140,7 @@ <h3>Method Details</h3>
       },
       &quot;name&quot;: &quot;A String&quot;, # Immutable. The resource name of the constraint. Must be in one of the following forms: * `projects/{project_number}/constraints/{constraint_name}` * `folders/{folder_id}/constraints/{constraint_name}` * `organizations/{organization_id}/constraints/{constraint_name}` For example, &quot;/projects/123/constraints/compute.disableSerialPortAccess&quot;.
       &quot;supportsDryRun&quot;: True or False, # Shows if dry run is supported for this constraint or not.
+      &quot;supportsSimulation&quot;: True or False, # Shows if simulation is supported for this constraint or not.
     },
   ],
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Page token used to retrieve the next page. This is currently not used.
diff --git a/docs/dyn/orgpolicy_v2.organizations.policies.html b/docs/dyn/orgpolicy_v2.organizations.policies.html
index 46702ab807e..e7114a9ec7b 100644
--- a/docs/dyn/orgpolicy_v2.organizations.policies.html
+++ b/docs/dyn/orgpolicy_v2.organizations.policies.html
@@ -131,6 +131,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -159,6 +162,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -188,6 +194,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -228,6 +237,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -256,6 +268,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -285,6 +300,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -351,6 +369,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -379,6 +400,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -408,6 +432,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -455,6 +482,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -483,6 +513,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -512,6 +545,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -564,6 +600,9 @@ <h3>Method Details</h3>
               },
               &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
               &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+              &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+                &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+              },
               &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
                 &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                   &quot;A String&quot;,
@@ -592,6 +631,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -621,6 +663,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -679,6 +724,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -707,6 +755,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -736,6 +787,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -777,6 +831,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -805,6 +862,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -834,6 +894,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
diff --git a/docs/dyn/orgpolicy_v2.projects.constraints.html b/docs/dyn/orgpolicy_v2.projects.constraints.html
index cb89317d601..4a62c9519d4 100644
--- a/docs/dyn/orgpolicy_v2.projects.constraints.html
+++ b/docs/dyn/orgpolicy_v2.projects.constraints.html
@@ -140,6 +140,7 @@ <h3>Method Details</h3>
       },
       &quot;name&quot;: &quot;A String&quot;, # Immutable. The resource name of the constraint. Must be in one of the following forms: * `projects/{project_number}/constraints/{constraint_name}` * `folders/{folder_id}/constraints/{constraint_name}` * `organizations/{organization_id}/constraints/{constraint_name}` For example, &quot;/projects/123/constraints/compute.disableSerialPortAccess&quot;.
       &quot;supportsDryRun&quot;: True or False, # Shows if dry run is supported for this constraint or not.
+      &quot;supportsSimulation&quot;: True or False, # Shows if simulation is supported for this constraint or not.
     },
   ],
   &quot;nextPageToken&quot;: &quot;A String&quot;, # Page token used to retrieve the next page. This is currently not used.
diff --git a/docs/dyn/orgpolicy_v2.projects.policies.html b/docs/dyn/orgpolicy_v2.projects.policies.html
index 1c2223aa7fb..7a9b383f384 100644
--- a/docs/dyn/orgpolicy_v2.projects.policies.html
+++ b/docs/dyn/orgpolicy_v2.projects.policies.html
@@ -131,6 +131,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -159,6 +162,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -188,6 +194,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -228,6 +237,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -256,6 +268,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -285,6 +300,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -351,6 +369,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -379,6 +400,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -408,6 +432,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -455,6 +482,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -483,6 +513,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -512,6 +545,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -564,6 +600,9 @@ <h3>Method Details</h3>
               },
               &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
               &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+              &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+                &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+              },
               &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
                 &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                   &quot;A String&quot;,
@@ -592,6 +631,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -621,6 +663,9 @@ <h3>Method Details</h3>
             },
             &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
             &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+            &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+              &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+            },
             &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
               &quot;allowedValues&quot;: [ # List of values allowed at this resource.
                 &quot;A String&quot;,
@@ -679,6 +724,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -707,6 +755,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -736,6 +787,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -777,6 +831,9 @@ <h3>Method Details</h3>
           },
           &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
           &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+          &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+            &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+          },
           &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
             &quot;allowedValues&quot;: [ # List of values allowed at this resource.
               &quot;A String&quot;,
@@ -805,6 +862,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
@@ -834,6 +894,9 @@ <h3>Method Details</h3>
         },
         &quot;denyAll&quot;: True or False, # Setting this to true means that all values are denied. This field can be set only in policies for list constraints.
         &quot;enforce&quot;: True or False, # If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.
+        &quot;parameters&quot;: { # Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { &quot;allowedLocations&quot; : [&quot;us-east1&quot;, &quot;us-west1&quot;], &quot;allowAll&quot; : true }
+          &quot;a_key&quot;: &quot;&quot;, # Properties of the object.
+        },
         &quot;values&quot;: { # A message that holds specific allowed and denied values. This message can define specific values and subtrees of the Resource Manager resource hierarchy (`Organizations`, `Folders`, `Projects`) that are allowed or denied. This is achieved by using the `under:` and optional `is:` prefixes. The `under:` prefix is used to denote resource subtree values. The `is:` prefix is used to denote specific values, and is required only if the value contains a &quot;:&quot;. Values prefixed with &quot;is:&quot; are treated the same as values with no prefix. Ancestry subtrees must be in one of the following formats: - `projects/` (for example, `projects/tokyo-rain-123`) - `folders/` (for example, `folders/1234`) - `organizations/` (for example, `organizations/1234`) The `supports_under` field of the associated `Constraint` defines whether ancestry prefixes can be used. # List of values to be used for this policy rule. This field can be set only in policies for list constraints.
           &quot;allowedValues&quot;: [ # List of values allowed at this resource.
             &quot;A String&quot;,
diff --git a/googleapiclient/discovery_cache/documents/orgpolicy.v2.json b/googleapiclient/discovery_cache/documents/orgpolicy.v2.json
index fcdf6379b15..2f2c72e1acc 100644
--- a/googleapiclient/discovery_cache/documents/orgpolicy.v2.json
+++ b/googleapiclient/discovery_cache/documents/orgpolicy.v2.json
@@ -930,7 +930,7 @@
 }
 }
 },
-"revision": "20241021",
+"revision": "20241129",
 "rootUrl": "https://orgpolicy.googleapis.com/",
 "schemas": {
 "GoogleCloudOrgpolicyV2AlternatePolicySpec": {
@@ -989,6 +989,10 @@
 "supportsDryRun": {
 "description": "Shows if dry run is supported for this constraint or not.",
 "type": "boolean"
+},
+"supportsSimulation": {
+"description": "Shows if simulation is supported for this constraint or not.",
+"type": "boolean"
 }
 },
 "type": "object"
@@ -1350,6 +1354,14 @@
 "description": "If `true`, then the policy is enforced. If `false`, then any configuration is acceptable. This field can be set only in policies for boolean constraints.",
 "type": "boolean"
 },
+"parameters": {
+"additionalProperties": {
+"description": "Properties of the object.",
+"type": "any"
+},
+"description": "Optional. Required for GMCs if parameters defined in constraints. Pass parameter values when policy enforcement is enabled. Ensure that parameter value types match those defined in the constraint definition. For example: { \"allowedLocations\" : [\"us-east1\", \"us-west1\"], \"allowAll\" : true }",
+"type": "object"
+},
 "values": {
 "$ref": "GoogleCloudOrgpolicyV2PolicySpecPolicyRuleStringValues",
 "description": "List of values to be used for this policy rule. This field can be set only in policies for list constraints."