How to add tags for APIs at version level apart from APIM service GUI

Hi,

We recently found an issue to add tags for APIs at version level.

Issue-1:
Adding tags for an API version is possible from APIM service GUI and same will be reflected in Developer portal at API version level but it's not possible to add tags from pipeline task.
See below snaps.





In pipeline agent job/tasks, there is no other ways to add this tags from "Deploy an Azure Resource Manager (ARM) template" https://github.com/microsoft/azure-pipelines-tasks/blob/master/Tasks/AzureResourceGroupDeploymentV2/README.md. Is this right one to add tags for API version?


How to add tags for APIs at version level from pipeline agent job?
Why tasks are not support to add tag in pipeline job?

Issue-2:

I have added tag in json file for one of the API version having couple of operations, this will not reflect in APIM service GUI or in developer portal anywhere, but this new tag "new-test-tag" will add only to "API tags" after saving.
Added tag as per documentation: https://github.com/OAI/OpenAPI-Specification/blob/main/versions/3.0.1.md#tagObject





Need help to fix the tagging issue here as well.
Why added tag in OpenAPI specification JSON file not updated in tags settings and developer portal API gallery?

CC: @AnRei123

Start with the AzureResourceGroupDeploymentV2 README linked in the issue and compare its documented pipeline inputs with the APIM service GUI behavior. Read the OpenAPI 3.0.1 Tag Object documentation linked in the report, then trace how API-version tags are represented in the developer portal. Done means the supported pipeline or specification path for version-level tags is identified and the reported behavior is resolved or documented.

Written by the indexing model from the issue text.