healthz: Add initiate_only field to CheckRequest - #355
Open
ejbrever wants to merge 1 commit into
Open
Conversation
ejbrever
force-pushed
the
healthz-checkrequest-initiate-only
branch
from
August 30, 2026 22:21
fb67ebe to
8f4ccd4
Compare
Contributor
Author
|
@dplore @robshakir could you please review? |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds the
initiate_onlyboolean field toCheckRequestinhealthz.proto, bumps thegnoi_versionto 1.4.0, and regenerateshealthz.pb.go.Motivation
Allows clients to initiate an asynchronous health check on a specific component path without blocking the RPC until the check or diagnostic artifact generation has finished. Clients can subsequently query results via
GetorList.