-
Bug
-
Resolution: Not a Bug
-
Blocker
-
None
-
-
User Experience
- Have a localServicesRouterDeployment.war, defining a root level tags element, e.g.:
tags: # Tag definition with a description for documentation - name: examples description: Operations related to SP examples ...
- Then, have a anotherLocalServicesRouterDeployment.war, defining a root level tags element, which include a tag with identical name but different description e.g.:
tags: # Tag definition with a description for documentation - name: examples description: Operations related to LSR examples ...
When deploying both the applications, the resulting OpenAPI document components element shows both the tag occurrences, with duplicated names:
--- tags: - name: examples description: Operations related to LSR examples - name: examples description: Operations related to SP examples ...
while the OpenAPI spec (see the tags element specification) states:
Each tag name in the list MUST be unique.
- blocks
-
WFLY-20567 MicroProfile OpenAPI subsystem does not allow multiple deployments to use the same endpoint
-
- Pull Request Sent
-
- clones
-
WFWIP-696 MicroProfile OpenAPI and multiple deployments: conflicting root level ".security" definitions appear in the final OpenAPI components element, but not at root level
-
- Open
-