Redundant API definitions in API gateway #1084
Description
Hi Team,
While going through the examples I noticed that in apigateway we are registering the individual endpoints again with enpointer, along with the request and response object definitions. But these are already defined in the individual services (in main.go).
So why to add this more redundant registration of independent API's? This doesn't seems to be elegant way of doing it.
Ideally I would expect my API gateway to just route to the registered services without any extra API configuration in API gateway code.
Can you please help me here?