[QUESTION] Advantages & Disadvantes of ApiOps Extractor vs Built-In APIM Git Repository

[nschoenberg]

Hi, im new to the ApiOps topic. I found good guidance in Microsoft documentation and Architecture Center as well as in this repo. From my current understanding the built-in Git Repository that comes with Azure APIM is doing a similar job as the ApiOps Extractor Pipeline. So ... is ApiOps easier to use? Or what are some advantages and disadvantages of using ApiOps compared to saving the configuration in the built-in APIM Git Repository? So yea, looking for general guidance and advise :)

Thanks in advance!

[github-actions]

🎉 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 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. 🎉

[waelkdouh]

@nschoenberg I am assuming you are referring to this.

The on-service git repository is one of many mechanisms to get APIs defined, which also include Terraform and Bicep. It doesn't cover all scenarios, and may be preferable to other techniques if it fits your operations model. APIOps has been proven to be suitable for scalable multi-team operations models.

You can start with the git edition and then transition to APIOps when you bump into requirements that preclude the git edition. We predict handling the API definition capabilities for multiple teams and/or large numbers of APIs that have their own lifecycle is likely to be the top reasons for reaching for APIOps.