Azure-devops-docs: Add ability to replace package

[piotrfalk]

Why you do not resolve common problems.

Please add ability to replace package on Azure DevOps Service. Why it's import? Let read following link:
https://octopus.com/docs/packaging-applications/creating-packages/nuget-packages/push-a-nuget-package-that-already-exists

---

Szczegóły dokumentu

⚠ Nie edytuj tej sekcji. Jest ona wymagana dla docs.microsoft.com ➟ Dołączanie problemu w usłudze GitHub.

• ID: 1475397e-1e4f-e51d-8cd8-29553112a059
• Version Independent ID: 4a8053f8-1ca5-a2aa-89ac-bbe0b2a6128f
• Content: Key concepts for Azure Artifacts
• Content Source: docs/artifacts/artifacts-key-concepts.md
• Product: devops
• GitHub Login: @elbatk
• Microsoft Alias: elbatk

[elbatk]

Hi @piotrfalk , thank you for your feedback. I'll relay this to the product team, but the most efficient way to give product-based feedback is through the Azure DevOps Developer Community, which is actively monitored by the product team. Going to close this as a docs issue now.

[infin8x]

In case other folks stumble on this thread: there are no plasn to change the immutability protections in Azure Artifacts. As documented, allowing packages to be overwritten leads to lots of icky and hard-to-debug side effects.

However, if you're publishing packages from Azure Pipelines, the NuGet task has an "Allow duplicates to be skipped" option that achieves the same effect that is described on the docs page you linked.

[Marina132000ae]

"Allow duplicates to be skipped" doesn't do the same thing. It won't update the version. We are using Maven and defined the repositories in a parent-pom. Then devops changed the url, so literally all of our projects have to change or I have to rebuild then entire feed. NuGet has an option that you can turn on/off to allow overwriting of versions. If you have to have immutability, could you just have it on promoted packages?

[elbatk]

Hi @Marina132000ae , sorry about the troubles. We don't have any plans to change how we view or enforce immutability. You could create a new feed, add the updated packages with updated poms, set up the current one as an upstream source and pull the remaining packages, and then delete the current (old) feed and rename the new one.

[Marina132000ae]

@elbatk That is a great idea! Thanks!

[gonzaloluna]

it makes no sense to enforce immutability on packages, it should be optional. Do I have to recreate the entire feed just because a package is corrupted or there was a human error during the process?