annotation for groups - Githubissues

Is your feature request related to a problem? Please describe. We'd like to have various separate json openapi export options to give to different integrators of our api.

We need the following:

one main swagger-ui which contains every controller. This is used by our team only.
Each 3rd party integrator should get a different set of controllers. Some controllers, such as authorisation, will be common. 3rd party should see only relevant parts.

The main goal is to export the openapi json for different customers, and allow post-processing such as readme.io.

What is the actual result using OpenAPI Description (yml or json)?

We are fine with either yml or json but each group should have its own json.

Describe the solution you'd like

apart from groupConfig.pathsToMatch and groupConfig.packagesToScan we would like to have annotation based approach on to of this mechanism.

i.e. annotate any method or controller with @SwaggerGroup("group1") and this annotation will take precedence over the pathsToMatch or packagesToScan configuration.

Describe alternatives you've considered We considered to go with groupConfig.pathsToMatch and groupConfig.packagesToScan only. But this forces our application to use url or package layout we would normally didn't use.

note we are currently on spring 2.x and use 1.8.0 library version.

springdoc / springdoc-openapi

annotation for groups #2697