# Data Object - HostProfileCompleteConfigSpec(vim.profile.host.HostProfile.CompleteConfigSpec)

Extends
  HostProfileConfigSpec
See also
  ComplianceProfile, HostApplyProfile, HostProfileConfigInfo, HostSystem
Since
  vSphere API 4.0

## Data Object Description

The HostProfileCompleteConfigSpec data object specifies the complete configuration for a host profile.

Properties

Name | Type | Description
--- | --- | ---
applyProfile* | HostApplyProfile | Profile that contains configuration data for the host.
customComplyProfile* | ComplianceProfile | User defined compliance profile. Reserved for future use.
disabledExpressionList* | xsd:string[] | List of expressions to be disabled. Each entry in the list specifies a ProfileExpression.id. All expressions are enabled by default. If you set disabledExpressionListChanged to True, the Profile Engine uses the contents of this list to replace the contents of the HostProfile.config.disabledExpressionList. The expression list is contained in the defaultComplyProfile. The Profile Engine automatically generates the default compliance profile when you create a host profile.
disabledExpressionListChanged | xsd:boolean | Flag indicating if this configuration specification contains changes in the disabledExpressionList. If False, the Profile Engine ignores the contents of the disabled expression list.
hostConfig* | HostProfileConfigInfo | Host profile configuration data and compliance information. If hostConfig is set, then the HostApplyProfile applyProfile and ComplianceProfile customComplyProfile should not be set in CompleteConfigSpec. Since vSphere API 6.5
validating* | xsd:boolean | If "false", then the host profile will be saved without being validated. The default if not specified is "true". This option should be used with caution, since the resulting host profile will not be checked for errors. Since vSphere API 6.0
validatorHost* | ManagedObjectReference to a HostSystem | Host for profile validation. This can be a host on which the profile is intended to be used. If you do not specify a validator host, the Profile Engine uses the HostProfile.referenceHost to validate the profile. Since vSphere API 5.0
Properties inherited from HostProfileConfigSpec
None
Properties inherited from ProfileCreateSpec
annotation, enabled, name
Properties inherited from DynamicData
None

*Need not be set
Show WSDL type definition
<complexType xmlns="http://www.w3.org/2001/XMLSchema" xmlns:vsan="urn:vsan" name="HostProfileCompleteConfigSpec"> <complexContent> <extension base="vsan:HostProfileConfigSpec"> <sequence> <element name="applyProfile" type="vsan:HostApplyProfile" minOccurs="0"/> <element name="customComplyProfile" type="vsan:ComplianceProfile" minOccurs="0"/> <element name="disabledExpressionListChanged" type="xsd:boolean"/> <element name="disabledExpressionList" type="xsd:string" minOccurs="0" maxOccurs="unbounded"/> <element name="validatorHost" type="vsan:ManagedObjectReference" minOccurs="0"/> <element name="validating" type="xsd:boolean" minOccurs="0"/> <element name="hostConfig" type="vsan:HostProfileConfigInfo" minOccurs="0"/> </sequence> </extension> </complexContent> </complexType>