-
Notifications
You must be signed in to change notification settings - Fork 67
Refine default enablement of gRPC health service #335
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
base: main
Are you sure you want to change the base?
Conversation
|
I will also add documentation where I will describe that server-side health in our case is disabled by default. |
|
👋🏻 @therepanic , thanks for the quick turnaround. However, we would like to have a team chat about this change before proceeding. We will get back w/ you shortly. |
|
It's more complicated than my comment in #334 implied. We don't want the health checks to be disabled by default if there actually is a |
|
You mean it should work like this?
|
|
Precisely |
|
Okay, I'll be back soon with some polished changes. |
Enable gRPC health by default only when a BindableService is present. Respect explicit spring.grpc.server.health.enabled overrides and add tests. Closes: spring-projectsgh-334 Signed-off-by: Andrey Litvitski <andrey1010102008@gmail.com>
|
I've slightly reworked my changes. They now incorporate the logic described above. I've also documented it. |
Document that server-side gRPC health is enabled by default only when a BindableService is present. Signed-off-by: Andrey Litvitski <andrey1010102008@gmail.com>
Remove the
BindableServicebean condition from gRPC health auto-configuration. Make server-side health opt-in by defaultspring.grpc.server.health.enabled=false. This allows exposing the health service as the only gRPC service without starting a server unexpectedly unless enabled.Closes: gh-334