Authentication to private Nuget Feed fails in Azure Pipelines (via Static Web App)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 881
- Forks
- 195
- Avg merge
- 20h 13m
- Merged PRs (30d)
- 13
Description
Bug Report
I'm using Oryx via the Azure Pipelines AzureStaticWebApp@0 task. When the API is built using Orxy I'm getting "error NU1301: Unable to load the service index for source" for all custom packages stored in our Azure DevOps. I can built the project successfully using the NuGetAuthenticate@1 task followed by dotnet publish (via DotNetCoreCLI@2).
Expected:
My expectation would be that Oryx is able to use the authentication provided by NuGetAuthenticate@1 and does not fail.
I did not find any documentation to otherwise authenticate with private Nuget feeds.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the AzureStaticWebApp@0 build path in Oryx and compare its NuGet handling with the NuGetAuthenticate@1 followed by DotNetCoreCLI@2 flow. Reproduce the private-feed failure with the reported NU1301 error; done means an authenticated feed works when the API is built through Oryx, with coverage for the supported pipeline path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp
- Domain
- authentication, build-system, ci-cd, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100