chore: Update discovery artifacts (#1390)
## Discovery Artifact Change Summary:
feat(sqladmin): update the api https://github.com/googleapis/google-api-python-client/commit/f2bb5e677634a0866836353bc40b26d40b1d044b
diff --git a/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html b/docs/dyn/osconfig_v1alpha.projects.locations.instanceOSPoliciesCompliances.html
index 879c01a..d53feb9 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](https://cloud.google.com/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](/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,9 +125,6 @@
"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.
},
@@ -158,7 +155,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](https://cloud.google.com/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](/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.
@@ -177,9 +174,6 @@
"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.
},