Allow 3rd-Party CredentialProviders

[stevek]

Currently Get-CredsFromCredentialProvider.ps1 is hard-wired to only allow CredentialProviders for pkgs.dev.azure.com and pkgs.visualstudio.com. To enable a 3rd party to write their own credential provider:

• remove lines 17-23 in that file

or

• provide a means to customize the sanity check
• provide a way to point to a custom CredentialProvder.

[SydneyhSmith]

@stevek thanks for opening this feature request, and providing some details--this change would break our current behavior but is something we will consider as we iterate on PowerShellGet 3.0 (particularly if this continues to draw user interest)

[skaempfer]

@SydneyhSmith Is there any official timeline or roadmap for PowerShellGet 3.0 (then presumably supporting NuGet 3.0)? This would be really informative for the users and help getting support for open tasks to reach this goal. Right now, connecting PowerShellGet with Azure DevOps artifacts is a real pain for me as well.

[SydneyhSmith]

@skaempfer we are targeting a preview release of PowerShellGet 3.0 at the end of this year--however this preview may not be feature complete

[skaempfer]

Looking forward to it! I'm fine with a mvp preview release :)

[justinsmits]

Hi all, has this issue been implemented in PowershellGet 3.0 and is there a date for the release? Apologies if I missed it somewhere. Thanks!

[Darsstar]

Since I was wondering myself, this seems to be the current status of things: In PowerShellGet 3.0 preview 14 the -CredentialInfo parameter was added which interacts with SecretManagement.