search

Azure / apiops

APIOps applies the concepts of GitOps and DevOps to API deployment. By using practices from these two methodologies, APIOps can enable everyone involved in the lifecycle of API design, development, and deployment with self-service and automated tools to ensure the quality of the specifications and APIs that they’re building.
https://azure.github.io/apiops
MIT License
328 stars 193 forks source link

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

Open ash9368 opened 3 weeks ago

ash9368 commented 3 weeks ago

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

github-actions[bot] commented 3 weeks ago 
  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 commented 2 weeks ago

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.