Repository navigation
[BUG] Running publisher after revision deletion remove whole API #709
Description
Release version
v6.0.1.3
Describe the bug
When I commit changes to an API with multiple revisions and remove one of the revisions, the publisher removes the entire API.
Expected behavior
I expect that only the revision removed in the commit will be deleted from the APIM instance.
Actual behavior
In reality, the entire API is removed from the APIM instance.
Reproduction Steps
I have an API with three revisions:
apis/
├── azerty-service/
├── azerty-service;rev=2/
└── azerty-service;rev=3/
I delete the folder apis/azerty-service;rev=2, commit the changes, and run the publisher for these updates.
As a result, the entire API azerty-service, including all its revisions, is removed from the APIM instance.
Reacted by Mangesh Paranjape
Activity
github-actions commentedon Nov 25, 2024
mangeshparanjape commentedon Mar 30, 2025
Anu update on this issue?
anotherRedbeard commentedon Aug 27, 2025
Wael Kdouh (@waelkdouh) and guythetechie for this one it looks like it runs the DELETE on the correct revision, but then you can see another DELETE call on the main api.
One workaround for this one is to remove the folder;rev= of the current revision in the repo and run the Publisher with the
publish-all-artifacts-in-repooption. So in the case of the issue author, if rev3 is the current revision, they would just need to remove theazerty-service;rev=3folder and run the publisher again withpublish-all-artifacts-in-repooption.fix: Prevent revision deletion from removing entire API
fix: Prevent revision deletion from removing entire API
fix: Prevent revision deletion from removing entire API