You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use config.extractor.yaml as below but nothing shows up in output, How to extract and deploy versioned api?
apiNames:
-orders-api-v1.
versionssetName
orders-api
Expected behavior
It should work same as versions api extraction and deployment. Is deployment extra too to create a Versionset ?
Actual behavior
Nothing gets extracted i get an empty artifact .
Reproduction Steps
Create a version to an API as URL path version identifier v1. and then add extract apiname as as Name in v1 version
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.
Please note that we are in the process of archiving this repository. We are transitioning to a new tool that will managed by the product team which can be found here. It shares the same dna of apiops with some improvements and better performance.
Activity
github-actions commentedon Aug 27, 2026
waelkdouh commentedon Aug 27, 2026
Please note that we are in the process of archiving this repository. We are transitioning to a new tool that will managed by the product team which can be found here. It shares the same dna of apiops with some improvements and better performance.
[-][BUG][/-][+][BUG] Not able to extract a versioned api[/+]mmohindra commentedon Aug 27, 2026
but can we look at the issue as is, we can look at new tool for future. v7.0.4 has the fix it seems. We can close issue for now