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 have one version set in which there is 2 version of API so when i run the APIOPS of that version i am having two different api on the branch but ideally it should be two api inside version set . my question is during the deployement from the dev to qa will it create the two different api or the 2 api inside the same version set ??
Expected behavior
there should be two api inside the version set in the branch after running the APIOPS
Actual behavior
there are two different api in the branch after running the APIOPS
Reproduction Steps
NA
The text was updated successfully, but these errors were encountered:
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.
Release version
APIM v1.0.0
Question Details
i have one version set in which there is 2 version of API so when i run the APIOPS of that version i am having two different api on the branch but ideally it should be two api inside version set . my question is during the deployement from the dev to qa will it create the two different api or the 2 api inside the same version set ??
Expected behavior
there should be two api inside the version set in the branch after running the APIOPS
Actual behavior
there are two different api in the branch after running the APIOPS
Reproduction Steps
NA
The text was updated successfully, but these errors were encountered: