NuGet Upload Difference between Enterprise and Basic Edition

[richard.gagliano_3594]

Hello,

I've noticed a difference in the NuGet feed behavior between our two instances of ProGet. We have two instances of ProGet, one is an Enterprise Edition with a cluster of 5 nodes. The other is a basic edition with a single node.

When uploading a NuGet package that already exists to the Basic Edition, we are able to see that there is a conflict, and are able to skip the package upload due to it being a duplicate.

When uploading a NuGet package that already exists to the Enterprise Edition cluster, we see that the package is re-created, and the conflict is not caught and skipped.

In looking at our two instances, all of the settings surrounding the feeds seem to be the same.

Is there a difference between these two editions surrounding the handling of duplicate NuGet packages? Our desire would be to have both feeds skip duplicate packages like our Basic Edition is doing.

Details:

Our NuGet push commands are as follows:

# Enterprise Edition Push
dotnet nuget push nupkgs\\*.nupkg -s ${ENTERPRISE_URL}/nuget/OUR-FEED/v3/index.json --skip-duplicate

# Basic Edition Push
dotnet nuget push nupkgs\\*.nupkg -s ${BASIC_URL}/nuget/OUR-FEED/v3/index.json --skip-duplicate

Thanks,

Rich

[atripp]

Hi @richard-gagliano_3594 ,

There's no difference between Enterprise and Basic edition with regards to feed behavior like this.

I'm not totally certain on the inner workings of --skip-duplicate in NuGet, but I believe that it simply suppresses/ignores errors related to pushing. You would have to reveiw the HTTP traffic using a tool like Fiddler to be sure.

I would check permissions in ProGet; it's most likely that your credentials (API Key) on one server has the Feed_OverwritePackage permission, and is therefore not throwing an error whe you push the package

Hope that helps!

Alana

[richard.gagliano_3594]

Hi Alana,

Thanks for confirming the consistent behavior between the two versions, and pointing us in the right direction. As you pointed out, the issue did stem from our CI/CD API key being overprivileged in our Enterprise edition instance. I reduced the privileges for the key, and duplicate packages are being skipped.

Thanks for your assistance.

Rich