Publishing openAPI specs dynamically, based on delivery endpoint configurations is a missing piece (without adding anything to our stack, since we use swagger already for the other endpoints).

Worth checking if we can decouple OpenAPI/Swagger support from the `RestDispatcherServlet`;

• publish the spec from a concrete endpoint implementation
• let the swagger UI follow other semi-static routes