-
-
Notifications
You must be signed in to change notification settings - Fork 76
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
Install PowerShell modules to a custom directory #125
Comments
If you give me a little direction on how you'd like this implemented, I can put together a PR. We use Whiskey to run our builds, and it has a |
Hey Aaron, you can already using the option target: It will save the modules in the target path. @{
PSDependOptions = @{
AddToPath = $true
Target = 'output\RequiredModules'
Parameters = @{}
}
InvokeBuild = 'latest'
PSScriptAnalyzer = '1.19.0'
Pester = '4.10.1'
Plaster = 'latest'
ModuleBuilder = 'latest'
} |
Thank. This issue can be closed. |
@gaelcolas Quick question: do you know, is the
then would |
I don't know. |
Thanks for the response @gaelcolas , I appreciate it! |
We have dozens of applications that use different versions of PowerShell modules when they get deployed. These modules are not pre-installed on the destination servers, nor do those servers have network access to any place from which they can be downloaded. Instead, we save all our to a PSModules directory in each application's repository (during builds) and include that directory in our deployment packages. Scripts import modules from that directory instead of globally.
Update PSDepend to support saving a module to a custom path instead of using "Install-Module".
The text was updated successfully, but these errors were encountered: