Skip to content

Remove the emit task's cc property #1073

Closed
@cdavernas

Description

@cdavernas

What would you like to be added?

Remove the emit task's cc property.

Proposal(s):

To remove the emit task's cc property, to address inherent issues described in detail below.

Alternative(s):

No response

Additional info:

As discussed in private conversations with both @fjtirado and @ricardozanini, while @modoodalvi’s original proposal is an excellent idea, it introduces multiple challenges and inconsistencies.

First, limiting the cc property to a single endpoint is overly opinionated; allowing an array of endpoints would be more flexible. However, this approach also raises routing concerns, which are better handled by the CEP chosen by each implementation, given the complexity involved and the lack of additional benefits to the specification.

Second, restricting the cc property to http(s) endpoints is both too limiting and overly prescriptive. Its current design, relying solely on a uri, prevents the use of widely adopted protocols like Kafka.

Community Notes

  • Please vote by adding a 👍 reaction to the feature to help us prioritize.
  • If you are interested to work on this feature, please leave a comment.

Metadata

Metadata

Assignees

Labels

area: examplesarea: specChanges in the Specificationchange: breakingA breaking change that will impact in a major version change.type: featuretype: regressionIndicates an issue caused by a regression or a feature that removes previously introduced functional

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions