Repository navigation
[Feature Request] Session scope for Register-PSRepository #65
Description
Activity
It would be also great if there was a scope option to register PSRepository on a system-wide level
Reacted by Brett JacobsonDoes being able to install to a specific location solve this scenario?
Thanks Gilbert Sanchez (@HeyItsGilbert) that use case makes sense to me for a system wide registration, I am wondering if the use case for a session scope registration is covered?
Sorry, I deleted my comment because I re-read the original request and realized that this request was specifically for a per Session scope.
If Publish Module allowed you alternatively specify a repo like data structure that might solve f0rt's issue.
Publish-Module Foo -Repo @{'Name' = 'My Repo'; 'Url' = 'myurl.com' }. No need to confirm of anything pre-existing and no clean up after the fact.
Team,
Can you please add session scope support for Register-PSRepository?
We have an internal build system that outputs PowerShell modules. Every successful build is published to an internal PSRepository (Artifactory server).
Every time we want to publish a module we have to deal with the following cases:
The problems described above can be avoided with Register-PSRepository operating on session level. Let me know if you have any questions.
Thanks,
Nedko