You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been thinking that we could easily add a parameter for the file name (defaulted to the current hard-coded Configuration.psd1) which would allow the file name to be specified ...
The idea would NOT be to let you customize the file names -- but to support different "sets" of configurations. That way if a module author wanted to switch between multiple named configurations they could just expose the name to their users ... or users who know you're using Configuration could just:
Get-Module YourModule |Import-Configuration-Set Special
So what should I call the parameter? We can't use Name because that's the parameter I'm using for the Module name.
Set (has the benefit of starting with a character that's unique among parameters)
Config
ConfigSet
Variant
???
The text was updated successfully, but these errors were encountered:
I've been thinking that we could easily add a parameter for the file name (defaulted to the current hard-coded
Configuration.psd1
) which would allow the file name to be specified ...The idea would NOT be to let you customize the file names -- but to support different "sets" of configurations. That way if a module author wanted to switch between multiple named configurations they could just expose the name to their users ... or users who know you're using Configuration could just:
So what should I call the parameter? We can't use
Name
because that's the parameter I'm using for the Module name.The text was updated successfully, but these errors were encountered: