You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the functions in this module, it is possible to puppetize and publish a module with DSC Resources which cannot be installed via puppet module install.
Expected Behavior
Modules published to the forge can be installed by end users.
Steps to Reproduce
# Validate the module is buildableNew-Item/tdsc -ItemType Directory
Import-Module-Name Puppet.Dsc
New-PuppetDscModuleNew-PuppetDscModule-PowerShellModuleName xremotedesktopsessionhost -Verbose -OutputDirectory /tdsc
# Show that the module built in this way is _not_ installable
puppet module install dsc-xremotedesktopsessionhost --version 2.0.0-0-1--trace
Additional Context
The root of this problem is with minitar as described in PUP-10924 and elaborated on in PDK-1684 - as long as we are unable to support long paths on module installation even when the operating system supports those paths we will have modules which are not installable by end users.
This Issue needs to be resolved before a 1.0.0 release can be cut.
The text was updated successfully, but these errors were encountered:
Describe the Bug
Using the functions in this module, it is possible to puppetize and publish a module with DSC Resources which cannot be installed via
puppet module install
.Expected Behavior
Modules published to the forge can be installed by end users.
Steps to Reproduce
Additional Context
The root of this problem is with minitar as described in PUP-10924 and elaborated on in PDK-1684 - as long as we are unable to support long paths on module installation even when the operating system supports those paths we will have modules which are not installable by end users.
This Issue needs to be resolved before a
1.0.0
release can be cut.The text was updated successfully, but these errors were encountered: