Usage of CloudEvents "subject" about spec

[erkist]

Your proposal makes a lot of sense to me. The type field would say what we are doing, and the subject field would say what we are doing it on/with/for.

I think we might need to provide a clear table in the spec stating for each event type what exactly the subject should be, just for clarity.

[afrittoli]

Your proposal makes a lot of sense to me. The type field would say what we are doing, and the subject field would say what we are doing it on/with/for.

I think we might need to provide a clear table in the spec stating for each event type what exactly the subject should be, just for clarity.

Yeah, that's a great idea.
The setup that I'm forming in my mind is, for each event a few elements will go in the CloudEvents context.
We could consider id and source as general cdevents context, mapped to CloudEvents context.
subject instead would map to a different event field based on the event type i.e. PIpelineRun ID, Environment ID etc..

[m-linner-ericsson]

With https://github.com/cdevents/spec/blob/main/spec.md#subject in mind: What would the subject look like in cloud events?

[afrittoli]

With https://github.com/cdevents/spec/blob/main/spec.md#subject in mind: What would the subject look like in cloud events?

Since CloudEvents include the source in the headers, subject should be the ID of the CDEvents subject, which is unique within the source.

[afrittoli]

Adressed by #35