-
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
Create Health Checks Provider to interact with Google Cloud #1763
Conversation
1834d41
to
270f6a8
Compare
/assign cezarygerard |
1 similar comment
/assign cezarygerard |
270f6a8
to
1e860f6
Compare
1e860f6
to
a535c7b
Compare
I personally a bit unsure about folder structure, maybe reviewers will have some opinion |
/assign bowei |
3b9a44f
to
b8c794c
Compare
b8c794c
to
667055e
Compare
667055e
to
9eb63b1
Compare
9eb63b1
to
907cf9c
Compare
0806833
to
cb02f09
Compare
Slavik, please add some more to the description what is our idea for splitting the logic into 4 layers
|
@@ -14,14 +14,13 @@ See the License for the specific language governing permissions and | |||
limitations under the License. | |||
*/ | |||
|
|||
package healthchecks | |||
package healthchecksl4 |
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 it's better to name the package l4healthchecks?
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.
WDYT?
/hold |
will squash after lgtm |
494a2df
to
9e61558
Compare
/lgtm |
9e61558
to
8ccb612
Compare
This separates business logic and handling health checks resources
8ccb612
to
5767597
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cezarygerard, 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 |
/unhold |
This separates business logic of managing L4 HealthChecks and interacting with Google Cloud API
We want to achieve following layered level logic
l4controller (handles workqueue for l4 services) -> l4 (for single service) -> l4healthchecks (health checks business logic) -> healthchecksprovider (no business logic, only interaction with gcp)
This makes composition better, testing and mocking should be also easier in the long run