router: add pluggable networking providers#85
Open
John Howard (howardjohn) wants to merge 1 commit into
Open
Conversation
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
2 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.
This PR extends the router to support pluggable network providers rather than a hardcoded Envoy. Envoy remains the default with no changes.
As we build out the feature set of substrate, we will have an expanded set of requirements on networking. For example, #15 (comment) expresses a need to inject credentials and a desire to be able to plug in the proxy of your choice. IMO this is very important: there are a number of projects coming up in this space specializing in the needs of agentic traffic that make sense to plug in here.