Azure
[BUG] Extractor does not work as expected for version-managed APIs
Release version
v4.10.2
Describe the bug
・Specification.yaml is incorrectly extracted for version-managed APIs (ex: v1/v2). Even though the API should be extracted as v1 API , the contents of specification.yaml are overridden with v2 contents. *In this case, the v2 API will be successfully extracted. Also, in any case, "files under operations" and "apiInformation.json" are successfully extracted. ・In some cases, v2 is extracted as v1.The main problems remain the same as described above. ・Completely random as to which API are incorrectly extracted.
Expected behavior
・specification.yaml will be extracted correctly. *Can be extract without any difference from the version on Azure Portal
Actual behavior
description in "Describe the bug"
Reproduction Steps
・Create API by importing from Azure Portal instead of using Publisher. ・Run Extractor several times and compare the differences. ・This bug is reproduced randomly.
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](https://avatars.githubusercontent.com/in/15368?v=4 "Published by a pub.dev verified publisher"){kind=small}
Please take a look at some open issues that address this topic. I know we are planning some changes in the upcoming versions.
@waelkdouh Thank you for your reply. I checked all open issues, but could not find any similar situation. I'm sorry, could you tell me the issue?