chore: Update discovery artifacts (#1381)
## Deleted keys were detected in the following stable discovery artifacts:
documentai v1 https://github.com/googleapis/google-api-python-client/commit/222030d8c1583f49657862a308b5eae41311d7e7
serviceconsumermanagement v1 https://github.com/googleapis/google-api-python-client/commit/e2046363f037151e02020ea178651b814c11761a
serviceusage v1 https://github.com/googleapis/google-api-python-client/commit/b79b21e71246ab6935214ca751125c83b1990167
## Deleted keys were detected in the following pre-stable discovery artifacts:
firebase v1beta1 https://github.com/googleapis/google-api-python-client/commit/6bd0412a11a1a55770415fdc76100b3c76a83a94
serviceconsumermanagement v1beta1 https://github.com/googleapis/google-api-python-client/commit/e2046363f037151e02020ea178651b814c11761a
serviceusage v1beta1 https://github.com/googleapis/google-api-python-client/commit/b79b21e71246ab6935214ca751125c83b1990167
## Discovery Artifact Change Summary:
feat(apigee): update the api https://github.com/googleapis/google-api-python-client/commit/37f31420ffc3adb1bdd23d7fc91f80701522aac8
feat(container): update the api https://github.com/googleapis/google-api-python-client/commit/514acdbf2c7eeaf6b1b9773c63b180131418ff57
feat(dlp): update the api https://github.com/googleapis/google-api-python-client/commit/7e3d1c4ab85d50307d42af3048f9a7dd47a2b9eb
feat(documentai): update the api https://github.com/googleapis/google-api-python-client/commit/222030d8c1583f49657862a308b5eae41311d7e7
feat(firebase): update the api https://github.com/googleapis/google-api-python-client/commit/6bd0412a11a1a55770415fdc76100b3c76a83a94
feat(ondemandscanning): update the api https://github.com/googleapis/google-api-python-client/commit/b77d12d24d17264123231dd86699fceada262440
feat(osconfig): update the api https://github.com/googleapis/google-api-python-client/commit/c541143744c4b077d0a044455a35d0de227a0bf6
feat(prod_tt_sasportal): update the api https://github.com/googleapis/google-api-python-client/commit/1e0f4a6e5e0bfde1ba4c06223d7fb02f63756690
feat(serviceconsumermanagement): update the api https://github.com/googleapis/google-api-python-client/commit/e2046363f037151e02020ea178651b814c11761a
feat(serviceusage): update the api https://github.com/googleapis/google-api-python-client/commit/b79b21e71246ab6935214ca751125c83b1990167
diff --git a/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html b/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html
index d53feb9..879c01a 100644
--- a/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html
+++ b/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html
@@ -106,7 +106,7 @@
Returns:
An object of the form:
- { # This API resource represents the OS policies compliance data for a Compute Engine virtual machine (VM) instance at a given point in time. A Compute Engine VM can have multiple OS policy assignments, and each assignment can have multiple OS policies. As a result, multiple OS policies could be applied to a single VM. You can use this API resource to determine both the compliance state of your VM as well as the compliance state of an individual OS policy. For more information, see [View compliance](/compute/docs/os-configuration-management/view-compliance).
+ { # This API resource represents the OS policies compliance data for a Compute Engine virtual machine (VM) instance at a given point in time. A Compute Engine VM can have multiple OS policy assignments, and each assignment can have multiple OS policies. As a result, multiple OS policies could be applied to a single VM. You can use this API resource to determine both the compliance state of your VM as well as the compliance state of an individual OS policy. For more information, see [View compliance](https://cloud.google.com/compute/docs/os-configuration-management/view-compliance).
"detailedState": "A String", # Output only. Detailed compliance state of the VM. This field is populated only when compliance state is `UNKNOWN`. It may contain one of the following values: * `no-compliance-data`: Compliance data is not available for this VM. * `no-agent-detected`: OS Config agent is not detected for this VM. * `config-not-supported-by-agent`: The version of the OS Config agent running on this VM does not support configuration management. * `inactive`: VM is not running. * `internal-service-errors`: There were internal service errors encountered while enforcing compliance. * `agent-errors`: OS config agent encountered errors while enforcing compliance.
"detailedStateReason": "A String", # Output only. The reason for the `detailed_state` of the VM (if any).
"instance": "A String", # Output only. The Compute Engine VM instance name.
@@ -125,6 +125,9 @@
"type": "A String", # Configuration step type.
},
],
+ "execResourceOutput": { # ExecResource specific output. # ExecResource specific output.
+ "enforcementOutput": "A String", # Output from Enforcement phase output file (if run). Output size is limited to 100K bytes.
+ },
"osPolicyResourceId": "A String", # The id of the OS policy resource.
"state": "A String", # Compliance state of the OS policy resource.
},
@@ -155,7 +158,7 @@
{ # A response message for listing OS policies compliance data for all Compute Engine VMs in the given location.
"instanceOsPoliciesCompliances": [ # List of instance OS policies compliance objects.
- { # This API resource represents the OS policies compliance data for a Compute Engine virtual machine (VM) instance at a given point in time. A Compute Engine VM can have multiple OS policy assignments, and each assignment can have multiple OS policies. As a result, multiple OS policies could be applied to a single VM. You can use this API resource to determine both the compliance state of your VM as well as the compliance state of an individual OS policy. For more information, see [View compliance](/compute/docs/os-configuration-management/view-compliance).
+ { # This API resource represents the OS policies compliance data for a Compute Engine virtual machine (VM) instance at a given point in time. A Compute Engine VM can have multiple OS policy assignments, and each assignment can have multiple OS policies. As a result, multiple OS policies could be applied to a single VM. You can use this API resource to determine both the compliance state of your VM as well as the compliance state of an individual OS policy. For more information, see [View compliance](https://cloud.google.com/compute/docs/os-configuration-management/view-compliance).
"detailedState": "A String", # Output only. Detailed compliance state of the VM. This field is populated only when compliance state is `UNKNOWN`. It may contain one of the following values: * `no-compliance-data`: Compliance data is not available for this VM. * `no-agent-detected`: OS Config agent is not detected for this VM. * `config-not-supported-by-agent`: The version of the OS Config agent running on this VM does not support configuration management. * `inactive`: VM is not running. * `internal-service-errors`: There were internal service errors encountered while enforcing compliance. * `agent-errors`: OS config agent encountered errors while enforcing compliance.
"detailedStateReason": "A String", # Output only. The reason for the `detailed_state` of the VM (if any).
"instance": "A String", # Output only. The Compute Engine VM instance name.
@@ -174,6 +177,9 @@
"type": "A String", # Configuration step type.
},
],
+ "execResourceOutput": { # ExecResource specific output. # ExecResource specific output.
+ "enforcementOutput": "A String", # Output from Enforcement phase output file (if run). Output size is limited to 100K bytes.
+ },
"osPolicyResourceId": "A String", # The id of the OS policy resource.
"state": "A String", # Compliance state of the OS policy resource.
},