Using container builds with private feeds

[jamiewinder]

When using the Lambda tools such as dotnet lambda package which results in a container build (e.g. AOT), what is the recommended approach when your project referencing privates Nuget feeds?

The [https://github.com/dotnet/dotnet-docker/blob/main/documentation/scenarios/nuget-credentials.md#using-the-azure-artifact-credential-provider](.NET docs) that relate to this lean heavily towards using a credentials provider which - since I'm using Azure DevOps for both the pipeline and the feed - makes a lot of sense. However it isn't obvious to me how / whether it's possible as all to do this with the CLI extensions.

[ashishdhingra]

@jamiewinder I also came across Managing NuGet Credentials in Docker Scenarios, which appears to be one of the approach to follow. Below are some references on AWS side;

• Using NuGet with AWS CodeArtifact
• Publish NuGet packages via Docker Release Container

Hope these help.

Thanks,
Ashish

[jamiewinder]

Thanks @ashishdhingra .

I have had some luck using NuGetPackageSourceCredentials_X environment variables (where X is a feed name) to provide the credentials, but only when calling dotnet publish myself. I'm not sure I can pass these environment variables to the dotnet lambda package command for it to forward to dotnet publish?

[sasha-simplyture]

Hi everyone.
Any news on this topic? In my opinion, this is quite critical, as organizations often use private Nuget feeds (repositories).

For now, I see only one way to do this: use the docker image (public.ecr.aws/sam/build-dotnet8 or lambda) without aws-extensions-for-dotnet-cli at all.