#443 Add batched reasons to TaskExecutionEvent Pull request opened by andrewwdye TL;DR Deprecate

TaskExecutionEvent.reason

in favor of

TaskExecutionEvent.reasons

to send batched events from flytepropeller, each with their own timestamp. Type ☐ Bug Fix ☑︎ Feature ☐ Plugin Are all requirements met? ☑︎ Code completed ☑︎ Smoke tested ☐ Unit tests added ☐ Code documentation added ☐ Any pending items have an associated Issue Complete description This change makes it possible to send kubernetes events as described in flyteorg/flyte#3825 without overloading propeller or admin with a large increase in TaskExecutionEvents. It deprecates

TaskExecutionEvent.reason

in favor of a repeated

TaskExecutionEvent.reasons

, which includes separate timestamps for each event. This allows for sending multiple reasons as part of the same event. Tracking Issue flyteorg/flyte#3825 Follow-up issue N/A flyteorg/flyteidl ✅ All checks have passed 13/13 successful checks