Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

Guardrails: Decoupling API schemas

未關閉
#1,227 0 則留言 0 個 reaction 已指派 1 人 在 GitHub 檢視

維護者通常 2 天內回覆

@Prajna1999 已經在處理了。

開始於 2026年10月5日。

評估

這個 Issue 還沒有評估資料。

描述

Is your feature request related to a problem?
The current integration of guardrails with the backend requires synchronization of API request-response schemas, leading to slower deployments when there are breaking changes in the guardrails schema.

Describe the solution you'd like

  • Explore importing the kaapi-guardrails GitHub repository into the kaapi backend.
  • Reuse Pydantic modules from the kaapi-guardrails in the kaapi backend.

Why is this enhancement needed?
This enhancement is necessary to ensure that deployments to guardrails are independent of changes required in the backend schema.

Original issue

Describe the current behavior
In the current implementation of guardrails being proxied through backend, when modifications to guardrails repo API request - response schema needs to be mirrored in kaapi-backend schema as well. This will slow down deployment since any breaking changes in guardarails schema will need to be synced with kaapi -backend schema forcing co-deployment.

Describe the enhancement you'd like
Explore Go like importing kaapi-guardrails github repo into kaapi backend and reuse pydantic modules into kaapi backend.

Why is this enhancement needed?
Required to make deployments into guardrails not dependent on mirror changes to backend.

Additional context

主要語言
Python
星號
18
分支
10
平均合併
3 天 20 小時
30 天內合併 PR
14

環境準備

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ProjectTech4DevAI/kaapi-backend 的其他 Issue

查看 ProjectTech4DevAI/kaapi-backend 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。