Description

kilasuit

opened on Jan 21, 2022

Issue body actions

Loking at the code it seems that there is no attempt to populate the FileList property in the psd1

It would be useful for this property to be populated when using ModuleBuilder

Activity

1. Jaykul commented on Jan 22, 2022

   

   Jaykul

   on Jan 22, 2022

   Member

   More actions

   Does anything use that property?
2. Jaykul

   closed this as completedon Jan 22, 2022
3. Jaykul

   reopened this on Jan 22, 2022
4. gaelcolas commented on Jan 22, 2022

   

   gaelcolas

   on Jan 22, 2022

   Contributor

   More actions

   Also, I think we may want to that later in the process?
   If we add things like platyps generated maml to the module, we'd have to update-modulemanifest anyway...

   Reacted by Joel Bennett
5. kilasuit commented on Jan 23, 2022

   

   kilasuit

   on Jan 23, 2022

   ContributorAuthor

   More actions

   It is useful for metadata quering reasons as well as in security validation, though I expect both aren't all that wide spread in their use.
   However I've have had issues in making sure it can be populated via a number of methods and that afterwards that the module can be published using PowerShellGet v2.2.5 to a local fileshare based repo. I have had no issue in doing this before with modules that have nested folders and files so I know it can be done.
6. Jaykul commented on Jan 23, 2022

   

   Jaykul

   on Jan 23, 2022

   Member

   More actions

   In an earlier project, I used that value to restrict which files would be packaged into the module package so that you could, for instance, have a config file in the folder next to the module, and trust it wouldn't be included in the package. However, when Microsoft released PowerShellGet, they said that since most people were not setting the value, they were going to package the entire contents of the module folder, regardless of this setting, creating a catch-22 situation: nobody sets it, so they ignore it, so nobody sets it...

   Since most people will need to use PowerShellGet to publish their modules, everyone now expects that behavior, and so (as far as I know) nothing in the OS, PowerShell, PowerShellGallery/PowerShellGet, or any antivirus actually references it either, as far as I know, perpetuating the fact that it can't be trusted for any particular use.

   All of that said -- I have no problem with setting it although (to avoid the issue @gaelcolas raised), you would have to build any binaries or help files into your module source before running Build-Module (and be sure to set CopyPaths) in order for ModuleBuilder to know all the files that need to be listed.
7. Jaykul

   added

   20 - Enhancement

   21 - HacktoberfestThese tickets are particularly easy to do without understanding the whole codebaseThese tickets are particularly easy to do without understanding the whole codebase

   on Sep 11, 2023

Issue actions