This topic contains 4 replies, has 2 voices, and was last updated by
April 30, 2016 at 12:03 pm #38432
I have found several modules I would like to use with DSC – eg;
The zip offered to download ends in -master.zip instead of the version name... which I cannot find in the package anywhere. Don't I need to rename this package with the version appended and then create a checksum – or has this changed? ..or maybe I'm just lost!? 🙂
May 1, 2016 at 3:27 am #38442ParticipantTopics: 5Replies: 261Points: -19Rank: Member
The version will be inside the .psd1 file that is the manifest of the module. It will be under ModuleVersion.
You still need that module zipped with the version appended and to create a checksum and send them both to the pull server.
May 1, 2016 at 6:28 am #38447
Ok thanks! What does the zip contents folder structure look like? Should it be:
PackageManagementProviderResource-220.127.116.11zip > PackageManagementProviderResource >
Each of those folders?
May 1, 2016 at 8:39 am #38450ParticipantTopics: 5Replies: 261Points: -19Rank: Member
Towards the bottom,in the section called DSC resource module package format, you should be removing the version folder.
Note that you downloaded a repository from github. That's why you had -master at the end of the file name to denote the master branch. Normally you would get the DSC resource package from the PowerShell Gallery, once you do get it from there, if you look at the folder structure you'll see it correct, but if you want to get it from github for the purposes of delivering it via the pull server to the nodes, you'll have to do those extra steps.
Hope this helped 🙂
May 1, 2016 at 9:10 am #38451
Very useful!!! Thank you very much!!!
The topic ‘How do I properly rename a module ending in *-master.zip?’ is closed to new replies.