-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Emit status check subtask events for V2 API #5961
Emit status check subtask events for V2 API #5961
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5961 +/- ##
==========================================
+ Coverage 70.57% 70.77% +0.20%
==========================================
Files 457 460 +3
Lines 17534 17706 +172
==========================================
+ Hits 12374 12531 +157
- Misses 4246 4251 +5
- Partials 914 924 +10
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one clarification but looks fine
TaskId: fmt.Sprintf("%s-%d", constants.StatusCheck, handler.iteration), | ||
Resource: r, | ||
Status: Failed, | ||
StatusCode: ae.ErrCode, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we don't add a Message
for failures? that's embedded in the actionable error then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
mhm, I'm not 100% on the original intent as this is from v1, but I think it's basically that in the case of a non-failure, we still want a message, and in the case of a failure, we put the message in the actionable error
Fixes: #5785
Related: #5368
Description
Event API V2 now emits
StatusCheckSubtaskEvents
, which give information about resources being updated during their deployment to a cluster.Most of this functionality is taken from V1
User facing changes (remove if N/A)
Users will not see
StatusCheckSubtaskEvents
emitted through the API.