[Discussion] Enable Contribution of Experimental Processing Extensions #233
Comments
**Commit Message**: This does the two re-organization of packages: * Renames `filterconfig` to `filterapi` * Put `extprocapi` into `filterapi/x` package The `filterapi/x` package will serve as an experimental package that facilitates the development of such features. Notably, custom routers etc while keeping the ability to introduce breaking changes at any release. This will be for advanced users as well as core contributors to iterate on some advanced features in the single repo. **Related Issues/PRs (if applicable)**: For #233 Signed-off-by: Takeshi Yoneda <[email protected]>
|
So I did a small refactoring of the Go packages before the v0.1.0rc release: #234. Based on that, the automatic model selection stuff proposed by @rootfs can live inside the experimental package https://github.com/envoyproxy/ai-gateway/blob/main/filterapi/x/x.go just like the custom router stuff (which requires the rebuild though). I think the semantics caching (#30) will also fall into the same style of "calling out from the extproc"? cc @Krishanx92 |
|
Sounds good! I'll rebase to the latest code and create a PR. |
|
yeah the initial PR should be only focused on the API of the external gRPC sever - no other stuff needed yet ! |
|
@mathetake it would be counterproductive to review an API protocol without a supporting PoC :D |
|
ok up to you - it would be helpful for reviews anyways! |
Description:
This Issue is for discussing how we can enable experimental data plane processing steps and control plane APIs
Relevant Links:
See notes from community meeting: https://docs.google.com/document/d/10e1sfsF-3G3Du5nBHGmLjXw5GVMqqCvFDqp_O65B0_w/edit?tab=t.0#heading=h.h7jtr1uxwvpi
cc @envoyproxy/ai-gateway-maintainers @envoyproxy/ai-gateway-assignable
The text was updated successfully, but these errors were encountered: