- 2.53.0 (latest)
- 2.51.0
- 2.50.0
- 2.49.0
- 2.48.0
- 2.47.0
- 2.46.0
- 2.45.0
- 2.44.0
- 2.43.0
- 2.42.0
- 2.41.0
- 2.39.0
- 2.38.0
- 2.37.0
- 2.36.0
- 2.35.0
- 2.34.0
- 2.33.0
- 2.32.0
- 2.31.0
- 2.30.0
- 2.29.0
- 2.26.0
- 2.25.0
- 2.24.0
- 2.23.0
- 2.22.0
- 2.21.0
- 2.20.0
- 2.19.0
- 2.18.0
- 2.17.0
- 2.16.0
- 2.15.0
- 2.14.0
- 2.13.0
- 2.11.0
- 2.10.0
- 2.9.0
- 2.8.0
- 2.7.0
- 2.6.0
- 2.5.6
- 2.4.3
- 2.3.2
public static interface OSPolicyAssignmentReport.OSPolicyComplianceOrBuilder extends MessageOrBuilder
Implements
MessageOrBuilderMethods
getComplianceState()
public abstract OSPolicyAssignmentReport.OSPolicyCompliance.ComplianceState getComplianceState()
The compliance state of the OS policy.
.google.cloud.osconfig.v1.OSPolicyAssignmentReport.OSPolicyCompliance.ComplianceState compliance_state = 2;
Returns | |
---|---|
Type | Description |
OSPolicyAssignmentReport.OSPolicyCompliance.ComplianceState |
The complianceState. |
getComplianceStateReason()
public abstract String getComplianceStateReason()
The reason for the OS policy to be in an unknown compliance state.
This field is always populated when compliance_state
is UNKNOWN
.
If populated, the field can contain one of the following values:
vm-not-running
: The VM was not running.os-policies-not-supported-by-agent
: The version of the OS Config agent running on the VM does not support running OS policies.no-agent-detected
: The OS Config agent is not detected for the VM.resource-execution-errors
: The OS Config agent encountered errors while executing one or more resources in the policy. Seeos_policy_resource_compliances
for details.task-timeout
: The task sent to the agent to apply the policy timed out.unexpected-agent-state
: The OS Config agent did not report the final status of the task that attempted to apply the policy. Instead, the agent unexpectedly started working on a different task. This mostly happens when the agent or VM unexpectedly restarts while applying OS policies.internal-service-errors
: Internal service errors were encountered while attempting to apply the policy.
string compliance_state_reason = 3;
Returns | |
---|---|
Type | Description |
String |
The complianceStateReason. |
getComplianceStateReasonBytes()
public abstract ByteString getComplianceStateReasonBytes()
The reason for the OS policy to be in an unknown compliance state.
This field is always populated when compliance_state
is UNKNOWN
.
If populated, the field can contain one of the following values:
vm-not-running
: The VM was not running.os-policies-not-supported-by-agent
: The version of the OS Config agent running on the VM does not support running OS policies.no-agent-detected
: The OS Config agent is not detected for the VM.resource-execution-errors
: The OS Config agent encountered errors while executing one or more resources in the policy. Seeos_policy_resource_compliances
for details.task-timeout
: The task sent to the agent to apply the policy timed out.unexpected-agent-state
: The OS Config agent did not report the final status of the task that attempted to apply the policy. Instead, the agent unexpectedly started working on a different task. This mostly happens when the agent or VM unexpectedly restarts while applying OS policies.internal-service-errors
: Internal service errors were encountered while attempting to apply the policy.
string compliance_state_reason = 3;
Returns | |
---|---|
Type | Description |
|