You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be very useful for operations to be able to be able to view the current config that a proxy is running at a given point in time.
Let's add two admin endpoints /clusters and /filterchain that returns a simplified JSON of the current cluster and filterchain respectively back to the caller. e.g:
I know envoy also has a /config_dump option which gives back basically everything. Does it make more sense to start there and provide all the info, than each of the different filter options, like /filterchain ?
That returns a JSON of the current config the proxy is running with
This includes a breaking change, as the FilterFactory to now needs to return
the config in addition to the filter it created.
Resolves#394
* Add a /config_dump endpoint
That returns a JSON of the current config the proxy is running with
This includes a breaking change, as the FilterFactory to now needs to return
the config in addition to the filter it created.
Resolves#394
It would be very useful for operations to be able to be able to view the current config that a proxy is running at a given point in time.
Let's add two admin endpoints /clusters and /filterchain that returns a simplified JSON of the current cluster and filterchain respectively back to the caller. e.g:
The text was updated successfully, but these errors were encountered: