You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure that for each phase we emit events consistently.
Details
For each phase, we emit K8s events that have no consistent value for the reason field.
We should take the opportunity to refactor the codebase to align event creation so it would be easier to move to a different standard or multiplexing the events to multiple channels. for example, publish a K8s event together with a CloudEvent and a Kafka message.
Acceptance Criteria
When an event is fired, the reason field has the following format: ${phaseName}${status}, where ${status} is one of the following: Started,Finished,Failed
The code to emit events is centralized making it easier to extend to other than just K8s events
DoD
Events have a consistent reason field
The text was updated successfully, but these errors were encountered:
Goal
Make sure that for each phase we emit events consistently.
Details
For each phase, we emit K8s events that have no consistent value for the
reason
field.We should take the opportunity to refactor the codebase to align event creation so it would be easier to move to a different standard or multiplexing the events to multiple channels. for example, publish a K8s event together with a CloudEvent and a Kafka message.
Acceptance Criteria
${phaseName}${status}
, where${status}
is one of the following:Started
,Finished
,Failed
DoD
The text was updated successfully, but these errors were encountered: