Skip to content
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

Merged
merged 2 commits into from
Jun 8, 2021

Conversation

MarlonGamez
Copy link
Contributor

@MarlonGamez MarlonGamez commented Jun 7, 2021

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.

@MarlonGamez MarlonGamez requested a review from a team as a code owner June 7, 2021 20:43
@MarlonGamez MarlonGamez requested a review from tejal29 June 7, 2021 20:43
@google-cla google-cla bot added the cla: yes label Jun 7, 2021
@codecov
Copy link

codecov bot commented Jun 7, 2021

Codecov Report

Merging #5961 (0f4a937) into master (20e00dc) will increase coverage by 0.20%.
The diff coverage is 90.90%.

Impacted file tree graph

@@            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     
Impacted Files Coverage Δ
pkg/skaffold/event/v2/event.go 76.16% <0.00%> (+2.83%) ⬆️
pkg/skaffold/deploy/resource/deployment.go 88.98% <50.00%> (-0.68%) ⬇️
pkg/skaffold/errors/errors.go 92.95% <71.42%> (-2.36%) ⬇️
pkg/skaffold/deploy/status/status_check.go 70.07% <100.00%> (+0.37%) ⬆️
pkg/skaffold/event/v2/status_check.go 100.00% <100.00%> (ø)
cmd/skaffold/app/cmd/inspect_profiles.go 63.15% <0.00%> (-29.15%) ⬇️
cmd/skaffold/app/cmd/inspect_modules.go 62.50% <0.00%> (-25.00%) ⬇️
pkg/skaffold/inspect/modules/list.go 83.33% <0.00%> (-16.67%) ⬇️
pkg/skaffold/inspect/buildEnv/add_gcb.go 71.92% <0.00%> (-2.54%) ⬇️
... and 19 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 20e00dc...0f4a937. Read the comment docs.

Copy link
Contributor

@nkubala nkubala left a 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,
Copy link
Contributor

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?

Copy link
Contributor Author

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

@MarlonGamez MarlonGamez merged commit 2ece888 into GoogleContainerTools:master Jun 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Have skaffold emit status check subtask protos
3 participants