[Question] Do api version sets need to be configured as part of the deployment pipeline?

[ochadwick-westminster]

Release version

APIOps Toolkit for Azure APIM v5.1.1

Question Details

Hello,

I've noticed in the apimartefacts extracted that in the apiinformation.json file under each API extracted, we have

{
  "properties": {
    "apiRevision": "1",
    "apiVersion": "v1",
    "apiVersionSetId": "/subscriptions/563xxxxx-dxx5-4xxe-axx1-62xxxxxxxxxxd1/resourceGroups/wcc-dev-apim-rg/providers/Microsoft.ApiManagement/service/wcc-dev-apim-external/apiVersionSets/65ce49a14fdbac95b92d5f16",
    "authenticationSettings": {},
    ...
}

I couldnt find anything referred to in the apiops documentation about the version sets, is this something that should be included in the environment configuration files? It does seem to be working without it, but with the subscription id being different between the apim instances the toolkit is deploying to (in our case) would this cause any impact?

I've done a call to view the version sets in our production environment post deployment and it looks to have set ones up using the correct subscriptions for the production subscription so it looks ok, but just keen to understand if these values are something we should be configuring in the publish files when working with versioned APIs.

Thanks
Oli

Expected behavior

N/A

Actual behavior

N/A

Reproduction Steps

N/A

[github-actions]

  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.

[waelkdouh]

Please search the outstanding issues. This topic has been discussed elsewhere.