Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Question] version set apiops , deploement from dev to qa enviroment #698

Open
ash9368 opened this issue Oct 29, 2024 · 2 comments
Open

Comments

@ash9368
Copy link

ash9368 commented Oct 29, 2024

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

Copy link

  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.

@guythetechie
Copy link
Contributor

This is not an ApiOps issue, unfortunately. Azure API Management treats different versions of an API as separate APIs.

When you publish to QA, you should still be able to see the two versions grouped together in the Azure portal under the same version set.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants