Update the routing state

PATCH 
/routing-state

Force an update of the routing state using the user provided routing state or by fetching the routing state from the engine first and then applying it to the configuration. No validation is performed on the user provided routing state, so it must be used only in the rare circumstances when it's not possible to fetch it from the engine. When physicalTenant is given, only that physical tenant's routing state is written; when omitted, the default physical tenant's routing state is written, regardless of which other physical tenants exist.

Request

Responses

202

Accepted

400

Invalid request.

404

The requested resource was not found.

409

Failed to accept request. Another topology change is in progress.

500

Internal error

502

Gateway failed to send request to the broker.

504

Request from gateway to broker timed out.