![]() The custom_insync feature first shipped in the puppet-resource_api version 1.8.14, which itself is only included in Puppet versions equal to or newer than 6.23.0 and 7.8.0 for the 6x and 7x platforms respectively. ![]() It is important to note that this feature is only supported with a version of puppetlabs-pwshlib equal to or higher than 0.9.0, in which the supporting code for the DSC Base Provider to implement custom insync was shipped.įinally, while this module's metadata says that the supported Puppet versions are 6.0.0 and up, the implementation of the validation_mode parameter relies on the custom_insync feature of the Puppet Resource API. You can set this value using the Puppet registry_value resource: registry_value We strongly recommend enabling long file path support on any machines using this module to avoid path length issues. Luckily in Windows 10 (build 1607+), Windows Server 2016 (build 1607+), and Windows Server 2019 there is now an option for supporting long file paths transparently! Several PowerShell modules with DSC Resources end up with very long file paths once vendored, many of which exceed the 260 character limit for file paths. This is important for troubleshooting and bug reporting, but doesn't impact your use of the module except that the end result will be that nothing works, as the dependency is not installed alongside this module! Long File Path Support This Puppet module includes two important things: the ruby-pwsh library for running PowerShell code from ruby and the base provider for DSC resources, which this module leverages.Īll of the actual work being done to call the DSC resources vendored with this module is in this file from the pwshlib module. The module also depends on the pwshlib module. While it is technically possible to add the Resource API functionality to Puppet 5.5.x, the DSC functionality has not been tested in this setup.įor more information on the Resource API, review the documentation. The Resource API ships inside of Puppet starting with version 6. The Resource API provides a simplified option for writing types and providers and is responsible for how this module is structured. This module, like all auto-generated Puppetized DSC modules, relies on two important technologies in the Puppet stack: the Puppet Resource API and the puppetlabs/pwshlib Puppet module. These DSC resources allow you to perform computer management tasks, such as renaming the computer, joining a domain and scheduling tasks as well as configuring items such as virtual memory, event logs, time zones and power settings.įor information on troubleshooting to determine whether any encountered problems are with the Puppet wrapper or the DSC resource, see the troubleshooting section below. ![]() The PowerShell module describes itself like this:ĭSC resources for configuration of a Windows computer. The functionality of this module comes entirely from the vendored PowerShell resources, which are pinned at v9.0.0. This is an auto-generated module, using the Puppet DSC Builder to vendor and expose the computermanagementdsc PowerShell module's DSC resources as Puppet resources. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |