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.
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-IDandX-PROJECT-IDpost resolving theX-API-KEYtoken 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.