Skip to content
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

Azure Artifacts Credential Provider Integration #1070

Open
rena0157 opened this issue Dec 3, 2022 · 5 comments · May be fixed by #1397
Open

Azure Artifacts Credential Provider Integration #1070

rena0157 opened this issue Dec 3, 2022 · 5 comments · May be fixed by #1397

Comments

@rena0157
Copy link

rena0157 commented Dec 3, 2022

Description

Essentially complete the same functions that using the NugetAuthenticate@1 does in a pipeline. Or even simply allowing for an additional step in the [AzurePipelines] that inserts the NugetAuthenticateTask before other tasks.

Usage Example

The proposed feature could be used as a part of the [AzurePipelines] auto-generation feature.

Alternative

There is no real good alternative that I have found. Right now you can do either of the following:

  • Manually add the NugetAuthenticate@1 task to the generated azure-pipelines.yml file
  • Manually implement the functionality of the Credential provider
@Megasware128
Copy link

Megasware128 commented Dec 19, 2022

@Basyras
Copy link

Basyras commented Jan 3, 2023

I am surprised it is not part of the default attribute yet. Not very elegant to force everyone write their custom attributes to perform something as common as this

@matkoch
Copy link
Member

matkoch commented Jan 4, 2023

@Basyras I suggest you get familiar with the contribution guidelines

@Basyras
Copy link

Basyras commented Jan 4, 2023

@matkoch looking back on what I just wrote i would express that in different way. Sorry. I didn't tried to be mean just tried to give feedback/ show support/upvote for this issues.

The comment is not driven by my personal interest I genuinely think it should be part of the nuke since I find it very common. Something I assume majority of developers using azure pipelines must have issue with.

I don't want just complain I am willing to contribute if you agree the issue should be addressed by nuke.

PS: Sorry for spamming the thread

@matkoch matkoch removed the triage label Nov 15, 2023
@ITDancer13
Copy link

I think, I've implemented what you're looking for in this PR #1397

From my point of view this is really helpful as it simplifies to work with private feeds in Azure DevOps

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants