Repository navigation
Backend: Streamline guardrails routes #1151
Description
Is your feature request related to a problem?
For the guardrails service being proxied through kaapi-backend to work, we need to add identical routes to kaapi-guardrails in kaapi-backend too. They must mirror the API request schema parsed without error by kaapi-guardrails service.
Also, kaapi-backend sends X-ORGANIZATION-ID and X-PROJECT-ID post resolving the X-API-KEY token through the payload for kaapi-guardrails to process i.e REST request verbs are independent of the above two arguments and only concerned with payloads being proxied.
Describe the solution you'd like
Original issue
Describe the current behavior
All 16 guardrails routes are mirrored in the Kaapi backend as a proxy layer over kaapi-guardrails (IP whitelisting + org/prod ID header). The 16 come from CRUD fan-out per endpoint.
Describe the enhancement you'd like
Common wrapper function for endpoints. Reuse that for individual guardrails endpoint.
Why is this enhancement needed?
Better maintainability.
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
[-]Kaapi Guardrails: Common router wrapper for Kaapi backend <---> kaapi guardrails APIs[/-][+]Backend: Streamline guardrails routes[/+]github-actions commentedon Sep 11, 2026
🎉 This issue has been resolved in version 1.7.0-main.3 🎉
The release is available on GitHub release
Your semantic-release bot 📦🚀