This repository was archived by the owner on Oct 9, 2023. It is now read-only.
Handle batched TaskExecutionEvent reasons #615
8000
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
TL;DR
Handle newly added
TaskExecutionEvent.reasons
field as part of flyteorg/flyteidl#443.Type
Are all requirements met?
Complete description
This change updates admin to process the recently added
TaskExecutionEvent.reasons
field, included to support sending batched reason events. This reduces load on both propeller and admin. Admin favors thereasons
field but falls back to thereason
field and prior behavior if empty.Tracking Issue
flyteorg/flyte#3825
Follow-up issue
N/A