docs: add README for in-tree plugins missing documentation#251
Open
noyitz wants to merge 1 commit into
Open
Conversation
github-actions
Bot
added
kind/documentation
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.
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Adds README.md files for the 7 in-tree plugins that were missing documentation:
datalayer/requestmetadata— in-flight request counts and token sumsmodelselector/scorer/costaware— input-token price scoringmodelselector/scorer/inflightrequests— least-loaded model scoringrequesthandling/basemodelextractor— LoRA adapter to base model resolutionrequesthandling/bodyfieldtoheader— generic body field to header extractionrequesthandling/modelselector— model-selector pipeline orchestratorresponsehandling/modelnametoheader— echo selected model as response headerEach README follows the existing pattern: plugin type, behavioral description, configuration with YAML example, parameters table, and inputs/outputs consumed.
Which issue(s) this PR fixes:
Fixes #213
Release note: