Sequence

    Sequence has three parts for the Spec:

    1. Steps which defines the in-order list of Subscribers, aka, which functions are executed in the listed order. These are specified using the messaging.v1.SubscriberSpec just like you would when creating Subscription. Each step should be Addressable.
    2. ChannelTemplate defines the Template which will be used to create Channels between the steps.

    Sequence Status

    Sequence has four parts for the Status:

    1. Conditions which detail the overall Status of the Sequence object
    2. ChannelStatuses which convey the Status of underlying Channel resources that are created as part of this Sequence. It is an array and each Status corresponds to the Step number, so the first entry in the array is the Status of the before the first Step.
    3. SubscriptionStatuses which convey the Status of underlying Subscription resources that are created as part of this Sequence. It is an array and each Status corresponds to the Step number, so the first entry in the array is the Subscription which is created to wire the first channel to the first step in the Steps array.

    For each of these examples below, we’ll use as the source of events.

    For the first example, we’ll use a 3 Step Sequence that is wired directly into the PingSource. Each of the steps simply tacks on “- Handled by ”, for example the first Step in the Sequence will take the incoming message and append “- Handled by 0” to the incoming message.

    For the next example, we’ll use the same 3 Step Sequence that is wired directly into the PingSource. Each of the steps simply tacks on “- Handled by ”, for example the first Step in the will take the incoming message and append “- Handled by 0” to the incoming message.

    The only difference is that we’ll use the Subscriber.Spec.Reply field to wire the output of the last Step to an event display pod.

    The only difference is that we’ll use the Subscriber.Spec.Reply field to wire the output of the last Step to another Sequence that does the same message modifications as the first pipeline (with different steps however).

    You can also create a Trigger which targets Sequence. This time we’ll wire PingSource to send events to a Broker and then we’ll have the Sequence emit the resulting Events back into the Broker so that the results of the can be observed by other Triggers.

    Was this page helpful?

    Sorry to hear that. Please tell us how we can improve.