Validating the Draft Software Specification

Before saving a draft and turning it into a desired state for a cluster, you can check whether the specification is complete and valid. You can also check whether the draft specification drifts in any way from the current state of the cluster.

The Drafts interface offers two methods for validating your draft. To check whether the draft is complete, there are no conflicts between the draft components, or unresolved dependencies, call the validate_Task(cluster_ID,draft_ID) method. Pass as arguments to this method the cluster and draft IDs. You validate whether there were any other drafts committed for this cluster, which will make the current commit operation invalid. The method also validates whether all components defined in the software specification are available in the depot metadata. This method does not run compliance checks against the cluster. To check whether all hosts in the cluster are compliant with the draft software specification, call the scan_Task(cluster_ID,draft_ID) method of the Drafts interface. Pass as arguments to this method the cluster and draft IDs. This method results in running a comparison between the draft specification and the current state of each host in the cluster.