Skip to content

Add sink property for emit task #1026

Closed
@modoodalvi

Description

@modoodalvi

Emit task allows workflows to publish events to event brokers or messaging systems.

However, based on the broker the runtime has to decide which sink to use. This information is missing in the emit task.

Proposal:

do:
  - emit:
      sink: 
        endpoint: 
          uri: https://mycoolendpoint.com/
          authentication: ...
      event:
        with:
          type: ...
          source: ...

Why is header or content based routing not enough?

Header or content based routing is done at the broker. For some brokers, the decision which sink / channel / topic / event bus to pick has to come first, before routing rules at these resources are applied.

The (domain) event should not contain routing information.

Metadata

Metadata

Assignees

Labels

area: specChanges in the Specificationchange: featureNew feature or request. Impacts in a minor version change

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions