Gateway controller should validate LLMProvider and LLMProxy policies
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 71
- Forks
- 111
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 110
Description
Please select the area the issue is related to
Area/Management (Management API or Management Portal UI), Area/AIPolicies (AI Gateway Policies, Guardrails)
Please select the aspect the issue is related to
Aspect/API (API backends, definitions, contracts, interfaces, OpenAPI)
Description
When i add a non existing policy to the LLMProvider i m not getting bad request. Gateway controller does not validate the policy it sends it to the policy engine. When i send the request to the gateway i see the policy engine is complaining the policy is not availble in the logs
Steps to Reproduce
Create a LLMProvider and attach a policy with wrong name, version wrong params.
Severity Level of the Issue
Severity/Major (Important functionality is broken. Should be prioritized. Doesn't need immediate attention)
Environment Details (with versions)
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the gateway controller path that handles LLMProvider creation and attached LLMProvider or LLMProxy policies, then trace how the request reaches the policy engine. Reproduce the invalid policy cases from the issue and verify that nonexistent names, wrong versions, and invalid parameters are rejected as Bad Request before the policy engine is called.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100