[BUG] Extractor pipeline extracted deleted items in APIM

[ghost]

Release version

4.10.3

Describe the bug

When running the Extractor pipeline it extracts items in APIM that had been deleted.

I have two instances where this happened:

• I created a Product in APIM which I later deleted. I created another product (different Id). The extractor extracted both the deleted product and the product currently there.
• I created an API with a GET operation. I later deleted that operation and recreated it with the same display name but different name/Id. The extractor extracted both the deleted operation and the new operation currently there.

Expected behavior

It should only extract what is currently in APIM

Actual behavior

It extracted deleted items

Reproduction Steps

Create an API with one GET operation.
Create a Product.
Run the extractor pipeline using 'extract all' and it successfully extracts one API with one operation and one Product.
Delete the original GET operation and create another GET operation (same display name, but different name).
Delete the original Product and create a different Product.
Run the extractor pipeline using 'extract all' and it extracts one API with two operations and two Products.

[guythetechie]

@eyvictorye - Note that you're running an unsupported version of ApiOps. We only support 5+.

Regardless, are you sure the product was deleted successfully? If I create a product in the portal and then try to delete it, I get an error message about an existing default subscription. I have to delete the subscription first before APIM lets me delete the product.

[ghost]

Yes, the product was deleted within APIM. And yes, in order to delete the product the subscription using the product needed to be deleted first.

[waelkdouh]

Yes, the product was deleted within APIM. And yes, in order to delete the product the subscription using the product needed to be deleted first.

Please make sure the issue is closed if your problem is resolved.

[ghost]

looks like it only extracts deleted items when it doesn't pick up the extractor configuration file properly. it's been working consistently now and i've updated to APIOps v5 and haven't had the issue anymore