[READ ONLY MIRROR] Envoy REST/proto API definitions and documentation. (grpc依赖)

You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Tag: Branch: Tree: 6c5bd3d375

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '6c5bd3d375'

${ noResults }

data-plane-api/envoy/config/rbac

History

data-plane-api(Azure Pipelines) 734944dcd5 rbac: add unified matcher for RBAC filters (#20877) ... Signed-off-by: Xie Zhihao zhihao.xie@intel.com Commit Message: rbac: add unified matcher for RBAC filters Additional Description: The patch add the matching API support for both RBAC network filter and HTTP filter. Users can configure rules and shadow rules in either policies or the matching API manner. There are some incompatibilities, TODOs and behavior changes compared to the policies way. RBAC matchers are not compatible with the matching API. URL path and CEL are not supported in the matching API. These matchers may come as custom matcher. Metadata is not supported in the matching API. These matchers may come as inputs. Connections and requests with no matcher matched will always be denied. Risk Level: Medium Testing: Unit and integration Docs Changes: API and configuration Release Notes: WIP Platform Specific Features: N/A Fixes #20623 Mirrored from https://github.com/envoyproxy/envoy @ 42cb84456d53d053eb1ae94680d07a74f4545a48		3 years ago
..
v2	protos: add support for go_option package (#17460)	3 years ago
v3	rbac: add unified matcher for RBAC filters (#20877)	3 years ago