-
Task
-
Resolution: Won't Do
-
Minor
-
None
-
None
As discussed in our meetings, we need to have a tags section added to the spec denoting which namespace they all belong to. See below for an example from cloud-connector's api.
{
"openapi": "3.0.0",
"servers": [
{
"description": "Cloud-Connector API",
"url": "/api/cloud-connector/"
}
],
"info": {
"description": "Cloud-Connector Service",
"version": "1.0.0",
"title": "Cloud-Connector Service"
},
"tags": [
{
"name": "api",
"description": "RESTful service"
},
{
"name": "connection",
"description": "Connection status operations"
}
],
"paths": {
"/v2/connections/{client_id}/message": {
"post": {
"tags": [
"api"
],
--snip--
}
Without this, we have a generation that produces a large diff with it wanting to use the namespace of 'Default' API.
- clones
-
RHCLOUD-22731 Ingress API is missing tags in openapi spec
-
- Closed
-
- relates to
-
-
- Closed
-