-
-
Notifications
You must be signed in to change notification settings - Fork 646
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Split remote providers into their own crates (#19958)
This does a no-functionality-change refactoring of the remote _store_ providers (backed by REAPI and OpenDAL). This splits the concept of a remote provider out into their own internal "surface" crate `remote_provider`, plus three crates that are (mostly) implementation-details of that one: - `remote_provider/remote_provider_traits` for the traits (and structs!) that the various providers have to implement - `remote_provider/remote_provider_reapi` for the gRPC/REAPI-backed provider - `remote_provider/remote_provider_opendal` for the OpenDAL-backed provider They're arranged like this: ```mermaid graph BT remote("process_execution/remote (existing)") store("fs/store (existing)") traits("remote_provider_traits (new)") grpc("remote_provider_reapi (new)") opendal("remote_provider_opendal (new)") selector("remote_provider (new)") grpc --> traits opendal --> traits selector --> grpc selector --> opendal remote -- for remote execution --> grpc remote --> selector store --> selector ``` Theoretically the new crates other than `remote_provider` are an implementation detail... except there's a helper in `remote_provider_reapi` that's used for the remote _execution_ in `process_execution/remote`, in addition to the byte store and action cache, hence the dependency there. This is one point of #19902, following up on #19827 (comment). The commits are individually reviewable, although the overall PR view gives a slightly more useful view of the overall file renames for some files.
- Loading branch information
Showing
30 changed files
with
689 additions
and
439 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Oops, something went wrong.