-
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
Refactor Add proto.ActionableErr to diag.Resource and deploy.Resource.Status #4390
Refactor Add proto.ActionableErr to diag.Resource and deploy.Resource.Status #4390
Conversation
e79d216
to
48066e3
Compare
…le error proto proto.ActionableErr In this PR, 1. For suggesting actionable errors for k8 infra errors, it would make sense to do it in the diag package. 2. Hence adding ActionableErr to diag.Resource package and propogating to depoyment status in skaffold.deploy.Resource.Status
48066e3
to
bdea994
Compare
Codecov Report
@@ Coverage Diff @@
## master #4390 +/- ##
==========================================
- Coverage 71.94% 71.87% -0.08%
==========================================
Files 325 325
Lines 12708 12722 +14
==========================================
+ Hits 9143 9144 +1
- Misses 2989 3000 +11
- Partials 576 578 +2
Continue to review full report at Codecov.
|
return r.ae | ||
} | ||
func (r Resource) StatusUpdated(another Resource) bool { | ||
return r.ae.ErrCode != another.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.
Should this code check if r.ae != nil && another.ae != nil
?
In this PR, I have added the actionable error message to the diagnostics package.
For suggesting actionable errors for k8 infra errors, it would make sense to do it in the diag package.
Got rid of
details
inskaffold.deploy.Resource.Status
to re-useproto.ActionableErr.Message
.Adding ActionableErr to daig.Resource package and propagating to deployment status in
skaffold.deploy.Resource.Status
Most of the code changes are in test. Very minor changes in source code files.
Fixes: #nnn
Related: Relevant tracking issues, for context
Merge before/after: Dependent or prerequisite PRs
Description
User facing changes (remove if N/A)
Follow-up Work (remove if N/A)