base_dsc_lite
: The base Puppet DSC type that all of the types inherit from. Do not use this directly.dsc
: Thedsc
type allows specifying any DSC Resource declaration as a minimal Puppet declaration.
The base Puppet DSC type that all of the types inherit from. Do not use this directly.
The following parameters are available in the base_dsc_lite
type.
namevar
A name to describe your resource, used for uniqueness.
The specific backend to use for this base_dsc_lite
resource. You will seldom need to specify this --- Puppet will
usually discover the appropriate provider for your platform.
The dsc
type allows specifying any DSC Resource declaration as a minimal Puppet declaration.
dsc {'iis':
resource_name => 'WindowsFeature',
module => 'PSDesiredStateConfiguration',
properties => {
ensure => 'present',
name => 'Web-Server',
}
}
The following properties are available in the dsc
type.
Valid values: present
An optional property that specifies that the DSC resource should be invoked.
The following parameters are available in the dsc
type.
Name of the DSC Resource module to use. For example, the xPSDesiredStateConfiguration DSC Resource module contains the xRemoteFile DSC Resource.
namevar
Name of the declaration. This has no affect on the DSC Resource declaration and is not used by the DSC Resource.
Hash of properties to pass to the DSC Resource.
To express EmbeddedInstances, the properties
parameter recognizes any key with a hash value that contains two keys —
dsc_type
and dsc_properties
— as a indication of how to format the data supplied. The dsc_type
contains the CimInstance name
to use,
and the dsc_properties
contains a hash or an array of hashes representing the data for the CimInstances. If the
CimInstance is
an array, we append a []
to the end of the name.
The specific backend to use for this dsc
resource. You will seldom need to specify this --- Puppet will usually
discover the appropriate provider for your platform.
Name of the DSC Resource to use. For example, the xRemoteFile DSC Resource.