higress-group/higress

OPA 插件优化，减少opa请求次数。

Open

#1,102 opened on Jul 8, 2024

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (1,219 forks)github user discovery
help wantedlevel/normalsig/wasm

Repository metrics

Stars
 (9,036 stars)
PR merge metrics
 (Avg merge 7d 9h) (18 merged PRs in 30d)

Description

我正在基于opa策略对 ai-proxy 插件代理的模型进行鉴权，opa 插件在 请求头和 请求体 阶段分别发起了请求，这儿可能需要更细化下需求。

在配置中允许用户根据自己的服务类型进行细粒度的鉴权配置，如用户只想基于header鉴权，那么就只需要配置 stage 为headers，其他阶段不做处理。如果需要读取body，才在body阶段处理。

或许可以加上类似配置:

stage:
- onheader
- onbody

Contributor guide

Research direction
Add a `stage` configuration field to the OPA plugin to allow users to specify which request stages (e.g., headers, body) should trigger OPA evaluation. Modify the plugin's request handler to conditionally execute OPA requests based on the configured stages, reducing unnecessary calls.
Tech stack
go
Domain
backendapi
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GoHigressOPA
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60