search

PowerShell / PowerShellGallery

228 stars 65 forks source link

Publish an item as unlisted #3

Open seanmcne opened 6 years ago

seanmcne commented 6 years ago

I'd like to request a feature to programmatically publish an item in the gallery as "Hidden" or a way to programmatically toggle the 'hidden' attribute for a given release/version .

An example: An update is published to the gallery that passed all initial tests but once in the gallery we found an issue with installing the module on some machines due to a code signing certificate problem.

In the future it would be nice to be able to publish as “hidden” and test module installation from the gallery and toggle the visibility once we confirm users 'in the wild' can install that specific version.

Thanks!

RStadlmair commented 6 years ago

Like this as all items are stored forever on the gallery and there should be some programmatic way to show/hide them from the public. Thx/R.

SydneyhSmith commented 5 years ago

This seems like a very similar ask to https://github.com/PowerShell/PowerShellGallery/issues/17

seanmcne commented 5 years ago

Sort of similar I suppose - it's important to have a way to "pre-deploy" a package that the public can't see so we can do a full test prior to opening it up to the pubic.

A flow of:

This would allow me to fully script & automate the dev / build process right up to publishing as 'hidden' so I can do a final test and push a button to 'release' it to the public.

Hope this makes sense - thanks!

SydneyhSmith commented 5 years ago

Yes, that explanation helps, thanks @seanmcne !

JustinGrote commented 4 years ago

Doesn't deploying modules as prerelease meet this need? I don't see the need for a net-new function.

Typical flow:

  1. Publish Module as prerelease
  2. If Prerelease module is broken, hide it
  3. Publish Release Module
  4. If broken release module, "fix forward" by hiding the existing module, publish a hotfix with a 0.0.x version bump, and publish the fixed module.

And before anything gets to the "publish" stage for any of the above, it's passed all your pester tests.

SteveL-MSFT commented 2 years ago

A customer recently brought this up. Basically they publish a set of modules to PSGallery all with the same version. They don't want users to download mixed versions of the modules. Ideally, they would want to publish them unlisted and have a way to flip a set of modules to be listed at once to make them public.