feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents - #11629
feat: As a user, I want to include the request body in the opa-input, so that I can reason about its contents#11629wistefan wants to merge 398 commits into
Conversation
|
Is there anything I can do to get this PR forward? |
|
This pull request has been marked as stale due to 60 days of inactivity. It will be closed in 4 weeks if no further activity occurs. If you think that's incorrect or this pull request should instead be reviewed, please simply write any comment. Even if closed, you can still revive the PR at any time or discuss it on the dev@apisix.apache.org list. Thank you for your contributions. |
|
@wistefan Please synchronize the master code to trigger all CI |
|
Hello! If I want this new implementation with the request body, what should I do? |
|
Hi @wistefan, please synchronize the latest master branch code to trigger the test. |
|
Hi @wistefan, please fix failed ci |
|
Hi @wistefan, do you have time to continue working on this PR? |
|
@Baoyuantop Yes, most likely beginning of next week |
|
@Baoyuantop Could you please appove the ci workflows? |
|
@wistefan, please fix failed ci |
|
Hello! What is the status of this? |
|
Need to fix the failed CI, waiting for a response from the author. |
|
Hello! Any news? |
…P workers when admin is disabled (apache#13515)
…hare a keepalive pool (apache#13516)
…r examples (apache#13543) * docs: fix mocking config note and invalid JSON in elasticsearch-logger examples - mocking: the docs say response_example and response_schema must not be configured together, but the schema uses anyOf (at least one) and the plugin prefers response_example when both are set. Correct the en/zh description accordingly. - elasticsearch-logger: the Admin API examples had a trailing comma after the only field ("index": "gateway",), making the JSON invalid for copy-paste. Remove it (en + zh, two places each). Signed-off-by: AlinsRan <alinsran@apache.org> * docs(mocking): clarify response_example/response_schema are not mutually exclusive The Required column said 'One of this or ...' / '二选一', implying the two fields are mutually exclusive, but the schema uses anyOf (at least one) and the plugin accepts both with response_example taking precedence. Align the column with that behavior. Signed-off-by: AlinsRan <alinsran@apache.org> --------- Signed-off-by: AlinsRan <alinsran@apache.org>
Signed-off-by: Abhishek Choudhary <shreemaan.abhishek@gmail.com>
|
@Baoyuantop @LuciaCabanillasRodriguez Hi, sorry, took far to long. But I think everything should be fixed now. |
|
Is there anything missing? |
Description
In order to make decisions based on the request body, the OPA-Plugin will also forward the body when configured to do so.
Fixes #11387
Checklist