eventStreamsRouteUpdate

Updates an existing route

Description: Update an existing route with the new configuration. All fields must be provided. The name, inputTopic, and subscriptionName fields are immutable and must match the existing route values. The route must be in STOPPED status before updating.

Input:

• input: EventStreamsRouteInput! — Updated route configuration. name, inputTopic, and subscriptionName must match existing values.

Error Codes:

• ROUTE_NOT_FOUND — No route with the given name exists in the environment.
• ROUTE_UPDATE_ERROR_RUNNING — Cannot update a running route. Stop the route first.
• ROUTE_TOPIC_LOOP — Input topic cannot be used as an output or default output topic.
• ROUTE_INVALID_INPUT — name, inputTopic, or subscriptionName does not match existing route.

Example:

mutation {
eventStreamsRouteUpdate(input: {
environmentId: "e0900205-7996-4795-9092-b9d2a21b77e9"
name: "order-routing"
inputTopic: "incoming-orders"
subscriptionName: "order-routing-sub"
defaultOutputTopic: "new-default-topic"
filters: [
{
name: "high-priority"
outputTopic: "priority-orders"
conditions: [
{
key: "priority"
value: "high"
valueType: STRING
operationType: EQUALS
}
]
}
]
}) {
environmentId
name
inputTopic
subscriptionName
defaultOutputTopic
status
filters {
name
outputTopic
conditions {
key
value
valueType
operationType
logicalOperator
}
}
}
}

eventStreamsRouteUpdate(
  input: EventStreamsRouteInput!
): EventStreamsRoute!

Arguments

eventStreamsRouteUpdate.input ● EventStreamsRouteInput! non-null input event-streams-admin

Type

EventStreamsRoute object event-streams-admin

A message routing rule that filters and routes messages based on metadata properties