feat(tonic-xds): add public bootstrap config builder & release alpha.3 - #2825
Open
YutaoMa wants to merge 1 commit into
Open
feat(tonic-xds): add public bootstrap config builder & release alpha.3#2825YutaoMa wants to merge 1 commit into
YutaoMa wants to merge 1 commit into
Conversation
YutaoMa
marked this pull request as ready for review
August 20, 2026 22:04
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
1 participant
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.
Motivation
Releasing alpha.3 to include the recent custom transport API additions, in order to test in other crates.
Solution
One gap identified while assessing the API production readiness: currently the only way to construct a bootstrap config to instantiate an xDS channel from is to go through a A27-formatted JSON string. This is more error prone than a typed builder, which is now introduced in this PR. We acknowledge that other gRPC implementations such as grpc-go explicitly marked its typed config builder as test only / experimental in anticipation of needing to change the config shapes, so here we marked relevant enums and fields as
#[non_exhaustive]and guarded them with checks to ensure forward compatibility.