-
Notifications
You must be signed in to change notification settings - Fork 303
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 healthchecksl4, change functions order, rename functions #1808
Refactor healthchecksl4, change functions order, rename functions #1808
Conversation
a46af84
to
6e7e0f1
Compare
/assign kl52752 |
d078f0c
to
a06994c
Compare
6488a06
to
b0cc6ff
Compare
err := l4hc.hcProvider.Delete(hcName, scope) | ||
if err != nil { | ||
// Ignore deletion error due to health check in use by another resource. | ||
if !utils.IsInUsedByError(err) { |
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.
maybe we should check the value of sharedHC to see if this error is really related to shared health check?
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.
I agree, that can be useful, but I don't want to change a lot of "logic" in this PR
Also, what if user decided to use our non-shared "healthcheck" for his own resources (which is weird case, but possible), so I am not sure, how we should act in this situation
b0cc6ff
to
004c214
Compare
004c214
to
804528d
Compare
- change functions order - extracted deleting health check to deleteHealthCheck function - rename EnsureHealthCheck -> EnsureHealthCheckWithFirewall, DeleteHealthCheck -> DeleteHealthCheckWithFirewall - removed unused return value from ensureHealthCheck
804528d
to
8b55dcc
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kl52752, panslava The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
No functional changes, just small refactoring
This is needed for Dual-Stack #1782, but doing this in separate PR