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
Hello Team,
I noticed that in my APIM instance tags were getting added even though I have no tags defined in the repo.
On further investigation, I found that when the specifications.yaml file has tags as part of the open api definition properties like below example:
openapi: 3.0.1
info:
title: Test API Books
description: Books API
version: v1
paths:
/list-all-comedy-books:
get: tags:
- comedyBooks
responses:
'200':
description: Success
content:
application/json:
--
then publisher is creating this Tag in APIM, in this example, i would see a tag called comedyBooks added to APIM.
Expected behavior
Tag is not added to apim unless explicitly defined under artifacts>tags folder
Actual behavior
Tag name is getting pulled from specifications file and being added to the API Tags in APIM.
Reproduction Steps
Create an open api spec with a tag value like below and then publish this to APIM.
openapi: 3.0.1
info:
title: Test API Books
description: Books API
version: v1
paths:
/list-all-comedy-books:
get: tags:
- comedyBooks
responses:
'200':
description: Success
content:
application/json:
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
v6.0.1
Describe the bug
Hello Team,
I noticed that in my APIM instance tags were getting added even though I have no tags defined in the repo.
On further investigation, I found that when the specifications.yaml file has tags as part of the open api definition properties like below example:
openapi: 3.0.1
info:
title: Test API Books
description: Books API
version: v1
paths:
/list-all-comedy-books:
get:
tags:
- comedyBooks
responses:
'200':
description: Success
content:
application/json:
--
then publisher is creating this Tag in APIM, in this example, i would see a tag called comedyBooks added to APIM.
Expected behavior
Tag is not added to apim unless explicitly defined under artifacts>tags folder
Actual behavior
Tag name is getting pulled from specifications file and being added to the API Tags in APIM.
Reproduction Steps
Create an open api spec with a tag value like below and then publish this to APIM.
openapi: 3.0.1
info:
title: Test API Books
description: Books API
version: v1
paths:
/list-all-comedy-books:
get:
tags:
- comedyBooks
responses:
'200':
description: Success
content:
application/json:
The text was updated successfully, but these errors were encountered: