The AddOnCompliance structure contains information that describe the compliance of the OEM add-on with respect to the add-on present in the target software specification.


current Optional

Current OEM add-on present on the host. unset if OEM add-on is not present on the host.

notifications Required

Notifications describing the compliance result.

status Required

The ComplianceStatus enumerated type contains the possible different status of compliance with respect to target version.
COMPLIANT : Target version is same as current version.
NON_COMPLIANT : Target version is greater than current version.
INCOMPATIBLE : Target state cannot be applied due to conflict or missing dependencies or the target state is lesser than the current version.
UNAVAILABLE : Drift check failed due to unknown error or check hasn’t happened yet and results are not available.


target Optional

Target OEM add-on present in the software specification. unset if OEM add-on is not present in the software specification.

JSON Example

	"notifications": {},
	"status": "COMPLIANT"


Was this page helpful?