apiops icon indicating copy to clipboard operation
apiops copied to clipboard

[Question] Extracted API definitions which no longer seem to exist

Open mattiabonanni opened this issue 1 year ago • 1 comments

Release version

v5.1.1

Question Details

Yesterday I've run the publishing pipeline to clean up some API definitions which were no longer in use. This morning when I ran the extractor pipeline I've noticed that the same API definitions where in the newly created PR.

In both Azure portal or APIM Management REST APIs those definition don't show up. I'm a bit confused from where the extractor is able to retrieve them.

As additional information:

  • This happened with a Development APIM;
  • Definitions, at least in dev environment, are also updated from our CD pipeline directly in the APIM;
  • Yesterday we also had an issue for which all definitions where accidentally deleted from the APIM (wrong configuration on our side in the configuration of the publisher pipeline which took the wrong, empty, folder) and they had to be recreated manually because the publisher was - and is - throwing some 409 or 422 errors. Not sure if's relevant, but still;

Expected behavior

Extractor retrieve only the current existing definitions.

Actual behavior

Extractor retrieve definitions which has been deleted.

Reproduction Steps

  • Publish some new API definition;
  • Run the extractor pipeline and accept the PR;
  • Manually remove the API definition from API Ops repo and the API Management;
  • Run the extractor pipeline again;

mattiabonanni avatar Mar 29 '24 09:03 mattiabonanni

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.

github-actions[bot] avatar Mar 29 '24 09:03 github-actions[bot]