Charles d'Avernas

On a side note, you'd probably be better off using the `correlationid` extension attribute defined for such use cases by the CloudEvent spec. In case that does not apply and/or...

You are right indeed, the mapping exists and is set to what seems a correct value, so it should now consume and correlate any events with the specified source/type/wfid. What...

@brampurnot I'm closing this as it is stale in `1.0.0-alpha`. Correlation engine has been refactored to use the new correlation key definitions defined in the DSL v1.0.0-alpha*.

@matthias-pichler-warrify you are totally right. AFAIR, we had agreed on `metadata` indeed, as we should avoid abbreviations whenever possible. Plus, `meta` is now archi bloated, thanks to Zuckerberg 🤣

As suggested by you in #978, I think we should add a new `redirects` boolean property, defaulting to `false`. As a matter of consequence, when it has been set to...

@ricardozanini This is IMHO definitly related to the DSL, as in some cases, an author might/have to explicitly authorize a redirect, and she might choose/have to to explicitly forbid it...

> Do you have a use case where the DSL author should set this property to the workflow level? @ricardozanini Sorry, I had overlook you last comment. There are a...

@JBBianchi @ricardozanini @fjtirado @matthias-pichler What do you guys think?

> @cdavernas so you are proposing that these scripts are also executed on the same container instance? Or just the same image? I was thinking of the container, but you...

> I think the GitHub actions comparison is a good starting point: It is an AWESOME, near perfect comparison indeed. And you are perfectly right: while the idea of reusing...