[Feature Request] Session scope for Register-PSRepository

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:

• Is the repository already registered?
• Is another repository with different name and the same SourceLocation already registered?
• If the repository is already registered and we want to deploy on different url (PublishLocation) we have to modify the existing registration
• Clean the build machine after build procedure (Unregister-PSRepository)
• If 2 parallel builds are running on the same build machine at the same time this can cause conflicts (dealing with the same shared resource)

The problems described above can be avoided with Register-PSRepository operating on session level. Let me know if you have any questions.

Thanks,
Nedko

Commencez par retracer l’implémentation existante de Register-PSRepository et la manière dont les enregistrements de référentiels sont stockés et associés à leur portée. Définissez le comportement attendu de la session, notamment l’isolation pour les builds parallèles et la sémantique du nettoyage, puis ajoutez une couverture pour ces cas avant de considérer la fonctionnalité comme complète.