-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
FileList property is not populated #112
Comments
Does anything use that property? |
Also, I think we may want to that later in the process? |
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. |
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. |
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
The text was updated successfully, but these errors were encountered: