Support for AWS CodeArtifact NuGet Repositories

Open
#371 2 comments 4 reactions 0 assignees View on GitHub

Maintainers usually reply within 7 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
aws, csharp, github-actions
Domain
cloud, devops

Research direction

Start by reviewing the setup-dotnet action and the workflow steps shown in the issue, especially the AWS.CodeArtifact.NuGet.CredentialProvider installation and dotnet nuget source commands. Determine how AWS CodeArtifact NuGet repositories should be exposed through the action, then validate the equivalent workflow on ubuntu-latest; done means the private action is no longer needed for this setup.

Written by the indexing model from the issue text.

Description

feature request investigation

Description:
My organization heavily uses AWS CodeArtifact for Private NuGet Package Hosting.

Currently we have a private action running the following lines on ubuntu-latest without much complaint:

- name: Prepare NuGet Repository
    run: | 
      dotnet tool install -g AWS.CodeArtifact.NuGet.CredentialProvider
      dotnet codeartifact-creds install
      dotnet nuget remove source nuget.org 
      dotnet nuget add source "${{ inputs.aws-code-artifact-nuget-source }}" -n "${{ inputs.nuget-feed-name }}"    
    shell: bash

Note: removal of the default nuget.org source is only necessary for us as our CodeArtifact Repository is configured as a pass through cache to nuget.org.

Justification:
Adding this into the upstream setup-dotnet action would allow us to deprecate our private action. I'm opening this as a feature request to gauge interest for others that desire this support.

Are you willing to submit a PR?
Absolutely! If additional interest, I'll pick this up in short order. If not, I'll manage a PR the next time I have to update my private action.

Dominant language
TypeScript
Stars
1.2k
Forks
579
Avg merge
6d 4h
Merged PRs (30d)
1

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from actions/setup-dotnet

All issues in actions/setup-dotnet

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.