Tihomir Surdilovic
Tihomir Surdilovic
use expression if you want as the string and have runtime eval it if that makes it easier, idk. but we are starting to look like google cloud workflow here..and...
ok well if you guys feel this is helpful then go for it 👍 i have 0 clue how this adds to portability tho, it just adds more enforcement from...
ok i think i understand this better now, I do like the namespace use but imo its a concept that if we add is something that could be applied to...
Think the reason for this is the event definition "source" property. If its consumed event then this has to be set to match the source where to consume from. if...
source is required attribute by CE https://github.com/cloudevents/spec/blob/main/cloudevents/spec.md#required-attributes
I think event defs are cheap to define. we could either leave it as is and deal with the duplication thats currently a must, or add on event defs another...
i personally like the eventRef kind lookup from the event def referenced, idk, seems natural to describe imo think it also helps with being able to switch out event defs...
ok :) from the eventRef perspective if its more clear to have "produceEventRef" and "consumeEventRef" or similar, yeah thats fine imo.
another thing we could do is change the event def "source" to "consumedSource" or something and then say that if the event is produced the runtime would set it..thats fair...
got it. ok thanks for explaining, ok so you want to offload the source to runtime if its not set? go for it