Skip to content
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

Alternate Config Files #24

Open
Jaykul opened this issue Oct 26, 2018 · 1 comment
Open

Alternate Config Files #24

Jaykul opened this issue Oct 26, 2018 · 1 comment

Comments

@Jaykul
Copy link
Member

Jaykul commented Oct 26, 2018

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
  • ???
@michaeltlombardi
Copy link

ConfigurationSet with Set as an alias makes the most sense to me.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants