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

Allow env var in apiKeys config #12821

Open
lonix1 opened this issue Aug 18, 2023 · 0 comments
Open

Allow env var in apiKeys config #12821

lonix1 opened this issue Aug 18, 2023 · 0 comments
Labels
Area:Authentication Area:Settings NuGet.Config and related issues Functionality:Push Priority:2 Issues for the current backlog. Type:Feature

Comments

@lonix1
Copy link

lonix1 commented Aug 18, 2023

NuGet Product(s) Involved

dotnet.exe, NuGet SDK

The Elevator Pitch

There are places where env vars are supported, but not for those bits that are useful for ci/cd.

Please allow us to read from an env var in this part of the nuget.config:

<apikeys>
  <add key="https://gitea.example.com/api/packages/myorg/nuget/index.json" value="%ACCESS_TOKEN%" />
</apikeys>

We could define the ACCESS_TOKEN env var in the pipeline, and nuget would detect it and use it for that specific nuget source.

(The nuget.config section with username/password is not useful in a ci/cd environment - we need to use api keys.)

Additional Context and Details

Using nuget in a ci/cd environment is a major pain, and has been for years (especially on linux, which is were most devops takes place). Please don't forget us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area:Authentication Area:Settings NuGet.Config and related issues Functionality:Push Priority:2 Issues for the current backlog. Type:Feature
Projects
None yet
Development

No branches or pull requests

3 participants