{"repo":"jbretsch/openapi-route-definition-locator","free":true,"listed":false,"github":"https://github.com/jbretsch/openapi-route-definition-locator","clone":"git clone https://github.com/jbretsch/openapi-route-definition-locator.git","description":"A RouteDefinitionLocator for Spring Cloud Gateway which creates route definitions dynamically based on OpenAPI (aka Swagger) definitions served by backend (micro)services.","language":"Groovy","stars":28,"topics":["java","api-gateway","microservices","openapi","spring","spring-boot","spring-cloud","spring-cloud-gateway","swagger"],"license":"MIT","category":"api-integrations-sdks","readme_excerpt":"OpenAPI Route Definition Locator for Spring Cloud Gateway The OpenAPI Route Definition Locator is a RouteDefinitionLocator for Spring Cloud Gateway. It dynamically creates route definitions based on OpenAPI (aka Swagger) definitions served by backend (micro)services. Key Benefits Let's assume you have a Kubernetes environment, where multiple microservices expose REST APIs, and some API endpoints need to be publicly accessible through a Spring Cloud Gateway, while others should remain internal. Managing these routes can be challenging, but the OpenAPI Route Definition Locator simplifies this process. Common Challenges Traditionally, you might resort to: - manually creating route definitions for each public API endpoint in a static configuration file for Spring Cloud Gateway or - using the DiscoveryClient Route Definition Locator to automatically generate a catch-all route for each microservice. However, both approaches have significant drawbacks: - Static route management becomes increasingly cumbersome as the number of microservices grows, especially when multiple teams are involved. Synchronizing API Gateway configurations with microservice releases in a large organization can be time-consuming and error-prone. - DiscoveryClient's automatic route generation by default exposes internal service identifiers in public URLs and results in tightly coupling public URLs with the internal service organization, reducing flexibility and making future changes more difficult. How OpenAPI","default_branch":null,"files":null,"tree":[],"storefront":"/r/jbretsch","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/jbretsch/openapi-route-definition-locator/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}