-ImportVariables/-ImportModules/-ImportFunctions #52

Activity

1. santisq commented on Jul 24, 2026

   

   santisq

   on Jul 24, 2026

   Owner

   More actions

   @God-damnit-all I don't like the idea of keep adding more parameters to the cmdlet. What can be done is make it so -Variables can take strings with wildcards then something like this works:

   $foo, $bar, $baz = 1, 2, 3
   .... | Invoke-Parallel { $foo, $bar, $baz } -Variables *

   Same for -Functions *. For -ModuleNames I will not consider it as needed since modules are automatically imported in the parallel scope due to discovery as long as they're correctly installed in one of the $env:PSModulePath paths.
2. God-damnit-all commented on Jul 24, 2026

   

   God-damnit-all

   on Jul 24, 2026

   Author

   More actions

   Sounds good!
3. santisq

   self-assigned this

   on Jul 27, 2026
4. santisq

   added

   documentationImprovements or additions to documentationImprovements or additions to documentation

   enhancementNew feature or requestNew feature or request

   on Jul 27, 2026
5. santisq commented on Jul 27, 2026

   

   santisq

   on Jul 27, 2026

   Last edited by santisq

   Owner

   More actions

   @God-damnit-all before this update, when -Functions was passed a non-existent name it'd throw:

   $"The function with name '{function}' could not be found."

   Which, after the update has now been changed to:

   $"Could not find any function matching the name or pattern '{function}'."

   Should it behave the same way for -Variables when passed a string that may or may not contain a wildcard? e.g.:

   $"Could not find any variable matching the name or pattern '{variable}'."
6. santisq

   linked a pull request that will close this issueAdds wildcard support to `-Variables` & `-Functions` Parameters #53on Jul 28, 2026
7. God-damnit-all commented on Jul 28, 2026

   

   God-damnit-all

   on Jul 28, 2026

   Last edited by God-damnit-all

   Author

   More actions

   Should it behave the same way for -Variables when passed a string that may or may not contain a wildcard? e.g.:

   Technically you can have wildcard characters in both variables and functions too (and not just their aliases):

   function * { "foo" }
   *
   # Output: foo
   
   ${*} = "bar"
   ${*}
   # Output: bar

   But as long as it honors wildcard escapes, it shouldn't be an issue.
8. God-damnit-all commented on Jul 28, 2026

   

   God-damnit-all

   on Jul 28, 2026

   Last edited by God-damnit-all

   Author

   More actions

   [I'm reposting this edit entirely just in case you rely on email alerts (because I changed my suggestion).]

   I suppose you could check if there's a literal match for the string before trying it as a wildcard, and if there's a literal match, continue with importing via wildcard, but issue a warning along with an instruction that if a user wants to suppress the warning, they can set $PSParallelPipelineNoLiteralWildcardWarning to $true (so you wouldn't have to add a switch just for this one edge-case).
9. santisq

   closed this as completedin #53on Jul 28, 2026
10. santisq commented on Jul 28, 2026

    

    santisq

    on Jul 28, 2026

    Owner

    More actions

    @God-damnit-all new version is available in the pwsh gallery: https://github.com/santisq/PSParallelPipeline/releases/tag/v1.3.0

    🎉React with 🎉1Reacted by God-damnit-all