-
Notifications
You must be signed in to change notification settings - Fork 150
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
Confusing package names in PowerShell Gallery #614
Comments
Ah, I have waited for @gaelcolas to fix the API key because the deploy failed. I did not know the PowerShell Team published that module to the Gallery, and of course that is why the deploy fails. 😕 Let's try to see if we can get that package transferred to DSC Community. Thanks for making me aware of this! |
It seems the old WebAdministrationDsc module is from this (now obsolete) working branch https://github.com/dsccommunity/WebAdministrationDsc/tree/WebAdministrationDsc. |
Hello folks, I'm looking forward to using the WebAdministrationDsc module, is there anything I can do to help resolve this naming issue? |
We have gotten an okey for DSC Community take over the module in PSGallery. We are now waiting for the transfer to happen, after that we will hastily release the new version that is waiting in this repo. |
Now WebAdministrationDsc has been released: https://twitter.com/dsccommunity/status/1571195505014894592 |
Since #601 it is confusing that the package name on PowerShell Gallery wasn't updated:
https://www.powershellgallery.com/packages/xWebAdministration/
And to make matters worse there is already another package with the new name 😞 :
https://www.powershellgallery.com/packages/WebAdministrationDsc/
... but at least only one version and last pushed in 2016.
Perhaps ⬇️ and ask if
WebAdministrationDsc
can be surrendered to this package?https://www.powershellgallery.com/packages/WebAdministrationDsc/0.1.0.0/ContactOwners
The text was updated successfully, but these errors were encountered: