-
Updated
Aug 10, 2021 - Go
loadbalancing
Here are 117 public repositories matching this topic...
-
Updated
Aug 5, 2021 - Shell
-
Updated
Dec 16, 2020 - Go
-
Updated
Jul 2, 2017 - Go
Timeout for waiting for the components/custom resources to launch or set up now is hardcoded. It's not reasonable since the GitHub Action is slow sometimes.
We may tidy up the timeout settings around the codebase and unify them with a configurable one, also, for the sake of easy to change, we may export an environment variable to control it.
-
Updated
Aug 9, 2021 - HCL
We tried to build dashboard docker image for ARM in #197 but failed. Since I could build dashboard docker image on m1 so there's nothing to do with the building process itself.
And since it stuck at yarn build
, a large chance is free Github Actions machine is lack of memory since we also deploy QEMU
to simulate arm environment, as [ref](https://stackoverflow.com/questions/59868448/rpc-error
-
Updated
Jan 19, 2021 - C#
-
Updated
Apr 16, 2021 - Go
-
Updated
Feb 27, 2020 - Go
-
Updated
Aug 9, 2019 - Go
-
Updated
May 24, 2021 - JavaScript
-
Updated
Sep 6, 2019 - C
-
Updated
Jun 15, 2017 - PHP
-
Updated
Jul 20, 2021 - JavaScript
-
Updated
Jan 18, 2019 - Java
-
Updated
May 11, 2018 - JavaScript
-
Updated
Jul 23, 2021 - PHP
-
Updated
Dec 19, 2020 - Go
-
Updated
Mar 19, 2019 - C
-
Updated
Apr 18, 2015 - Python
-
Updated
Jun 12, 2021 - JavaScript
-
Updated
Dec 7, 2017 - Java
-
Updated
Mar 2, 2019
-
Updated
Aug 2, 2021
-
Updated
Feb 9, 2021 - Java
-
Updated
Jun 24, 2021 - Fortran
-
Updated
Feb 10, 2020
Improve this page
Add a description, image, and links to the loadbalancing topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the loadbalancing topic, visit your repo's landing page and select "manage topics."
Issue description
在Consumer中添加 consumer-restriction 插件,里面的 type 能否支持下route_id,这样我们就能基于 consumer 的纬度来限制能访问到的 route,现在的版本我看了下只支持 consumer_name 和 service_id,即只能在 route 纬度来限制 consumer 或者 只能在 consumer 纬度来限制能访问的 service。
需求场景:同一组service下可以有多个route,但是可能有部分route是不用鉴权的或者需要额外申请才给开通,如果能在consumer纬度支持一下 route_id,那样就能更精细化的赋权,且不用每个用户来申请权限都需要对route接口发起一个PATCH请求。
插件文档:https://apisix.apache.org/docs/apis