Chiebot-Mirror
/
data-plane-api
mirror of https://github.com/envoyproxy/data-plane-api.git
8
0
Fork 0
Code Issues Projects Releases Wiki Activity
[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.
620 Commits
2 Branches
0 Tags
17 MiB
Tag: Branch: Tree: 27371599d3
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '27371599d3'
${ noResults }
data-plane-api/docs/BUILD

76 lines
3.3 KiB
Raw Normal View History Unescape

Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
licenses(["notice"]) # Apache 2
package_group(
name = "docs",
packages = [
"//docs",
],
)
# TODO(htuch): Grow this to cover everything we want to generate docs for, so we can just invoke
# bazel build //docs:protos --aspects tools/protodoc/protodoc.bzl%proto_doc_aspect --output_groups=rst
proto_library(
name = "protos",
deps = [
admin: add json serialized proto for /clusters (#3478) Added the /clusters?format=json admin endpoint along with a proto representation of /clusters. Risk Level: Low Testing: Added a unit test for the new format. Docs Changes: Added a brief description on the admin docs and linked to the more detailed proto definition. Release Notes: Added release notes. Fixes #2020 Signed-off-by: Matt Rice <mattrice@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 64605338ef040a949c5ea205bdd472a8fe42306c
7 years ago
"//envoy/admin/v2alpha:clusters",
admin: complete /config_dump (#3340) This completes initial implementation of the /config_dump admin endpoint, allowing for detailed display of the currently loaded Envoy configuration, including versions of each resource. Note that this does not include output for EDS. That work is tracked in https://github.com/envoyproxy/envoy/issues/3362. Fixes https://github.com/envoyproxy/envoy/issues/2421 Fixes https://github.com/envoyproxy/envoy/issues/2172 *Risk Level*: Low *Testing*: Unit/integration *Docs Changes*: Added *Release Notes*: Added Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ a2a5fc1df1541ebe0b0cd761f3e77212dbf70e5f
7 years ago
"//envoy/admin/v2alpha:config_dump",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/api/v2:cds",
"//envoy/api/v2:discovery",
"//envoy/api/v2:eds",
"//envoy/api/v2:lds",
"//envoy/api/v2:rds",
"//envoy/api/v2/cluster:circuit_breaker",
"//envoy/api/v2/cluster:outlier_detection",
"//envoy/api/v2/core:protocol",
"//envoy/api/v2/listener",
"//envoy/api/v2/ratelimit",
"//envoy/api/v2/route",
access log service: cleanup and docs (#3494) Fixes https://github.com/envoyproxy/envoy/issues/743 This is a general cleanup of all of the access logging documentation. I have reorganized a bunch of things and hidden the various gRPC logging fields that are not implemented yet. I've also moved the existing tap protos into a new "output" directory. This is the best name I could come up for cleanly separating output data that might be stored outside of any service or configuration. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ c15019e79c832d9f0a09468affaadabc4be3e115
7 years ago
"//envoy/config/accesslog/v2:als",
"//envoy/config/accesslog/v2:file",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/bootstrap/v2:bootstrap",
"//envoy/config/filter/accesslog/v2:accesslog",
"//envoy/config/filter/http/buffer/v2:buffer",
authz_filter: configuration to support Ambassador authorization flow (#563) This PR includes the necessary modifications in support of envoyproxy/envoy#2828. Added additional configuration to ext_authz.proto so that the filter is able to call an HTTP/1.1 authorization service. In external_auth.proto, added a nested message to CheckResponse that allows the authorization service to pass additional HTTP response attributes back to the authz filter. Signed-off-by: Gabriel <gsagula@gmail.com>
7 years ago
"//envoy/config/filter/http/ext_authz/v2alpha:ext_authz",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/filter/http/fault/v2:fault",
"//envoy/config/filter/http/gzip/v2:gzip",
Header to metadata filter (#2436) (#3633) Add support for extracting dynamic metadata from requests. This can then be used as static metadata would be used (e.g.: for subset load balancer metadata matches, logging, etc). Risk Level: Low Testing: unit-test Docs Changes: Basic docs. Release Notes: N/A Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 827c0a548ab38d55debe00587ee27253786befad
7 years ago
"//envoy/config/filter/http/header_to_metadata/v2:header_to_metadata",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/filter/http/health_check/v2:health_check",
ip tagging filter: update proto and add documentation (#506) Updates the L7 IP tagging filter proto, v1 configuration documentation and overview documentation. Signed-off-by: Constance Caramanolis <ccaramanolis@lyft.com>
7 years ago
"//envoy/config/filter/http/ip_tagging/v2:ip_tagging",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/filter/http/lua/v2:lua",
"//envoy/config/filter/http/rate_limit/v2:rate_limit",
authz: RBAC HTTP filter + utilities (#3455) Signed-off-by: Chris Roche <croche@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ d519097e9d0f914cac7362f8bafc8623ba2c09db
7 years ago
"//envoy/config/filter/http/rbac/v2:rbac",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/filter/http/router/v2:router",
"//envoy/config/filter/http/squash/v2:squash",
"//envoy/config/filter/http/transcoder/v2:transcoder",
"//envoy/config/filter/network/client_ssl_auth/v2:client_ssl_auth",
"//envoy/config/filter/network/ext_authz/v2:ext_authz",
"//envoy/config/filter/network/http_connection_manager/v2:http_connection_manager",
"//envoy/config/filter/network/mongo_proxy/v2:mongo_proxy",
"//envoy/config/filter/network/rate_limit/v2:rate_limit",
"//envoy/config/filter/network/redis_proxy/v2:redis_proxy",
"//envoy/config/filter/network/tcp_proxy/v2:tcp_proxy",
s/grpc_credentials/grpc_credential/ in api (#3595) Fixes #3584 Description: Risk Level: Low Testing: existing tests / CI Docs Changes: Release Notes: Signed-off-by: Lizan Zhou <zlizan@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e931af6a84013a934a40f817d941e6b745cbca26
7 years ago
"//envoy/config/grpc_credential/v2alpha:file_based_metadata",
health check: add custom health checker (#596) This patch adds the extension health check, with redis as the first example. Signed-off-by: Dhi Aurrahman <dio@rockybars.com>
7 years ago
"//envoy/config/health_checker/redis/v2:redis",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/metrics/v2:metrics_service",
"//envoy/config/metrics/v2:stats",
"//envoy/config/ratelimit/v2:rls",
authz: RBAC HTTP filter + utilities (#3455) Signed-off-by: Chris Roche <croche@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ d519097e9d0f914cac7362f8bafc8623ba2c09db
7 years ago
"//envoy/config/rbac/v2alpha:rbac",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/config/trace/v2:trace",
tap/fuzz: transport socket extension for traffic capture. (#3244) * tap/fuzz: transport socket extension for traffic capture. This PR introduces a transport socket extension that wraps a given transport socket, interposes on its plain text traffic and records it into a proto trace file on the filesystem. This can be used for a number of purposes: 1. As a corpus for fuzzing the data plane. 2. Converted to PCAP using a soon-to-be-written utility, allowing existing tools such as Wireshark to be used to decode L4/L7 protocol history in the trace. Essentially this lets us take advantage of the PCAP ecosystem. Relates to #1413 and #508. Risk Level: Low (opt-in). Testing: New SSL integration tests, demonstrating plain text intercept. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 6c7a91733469f76381487f9ca78bdece6825c8c9
7 years ago
"//envoy/config/transport_socket/capture/v2alpha:capture",
access log service: cleanup and docs (#3494) Fixes https://github.com/envoyproxy/envoy/issues/743 This is a general cleanup of all of the access logging documentation. I have reorganized a bunch of things and hidden the various gRPC logging fields that are not implemented yet. I've also moved the existing tap protos into a new "output" directory. This is the best name I could come up for cleanly separating output data that might be stored outside of any service or configuration. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ c15019e79c832d9f0a09468affaadabc4be3e115
7 years ago
"//envoy/data/accesslog/v2:accesslog",
health check: structured active healthcheck logging (#3176) Signed-off-by: James Sedgwick <jsedgwick@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ a5da0783828d21a2a90d1088134967a7201f0210
7 years ago
"//envoy/data/core/v2alpha:health_check_event",
access log service: cleanup and docs (#3494) Fixes https://github.com/envoyproxy/envoy/issues/743 This is a general cleanup of all of the access logging documentation. I have reorganized a bunch of things and hidden the various gRPC logging fields that are not implemented yet. I've also moved the existing tap protos into a new "output" directory. This is the best name I could come up for cleanly separating output data that might be stored outside of any service or configuration. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ c15019e79c832d9f0a09468affaadabc4be3e115
7 years ago
"//envoy/data/tap/v2alpha:capture",
"//envoy/service/accesslog/v2:als",
Add documentation for external authorization filter. (#3379) Signed-off-by: Saurabh Mohan <saurabh+github@tigera.io> Mirrored from https://github.com/envoyproxy/envoy @ a2abe7a4fae83cc2ad45700e59f4be52cbd3baac
7 years ago
"//envoy/service/auth/v2alpha:attribute_context",
"//envoy/service/auth/v2alpha:external_auth",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
"//envoy/service/discovery/v2:ads",
"//envoy/service/load_stats/v2:lrs",
"//envoy/service/metrics/v2:metrics_service",
access log: runtime filter enhancements (#490) 1) Add ability to runtime filter to configure default, divisor, and whether independent randomness is used. 2) Also add LE to the comparison filter. Signed-off-by: Matt Klein <mklein@lyft.com>
7 years ago
"//envoy/type:percent",
Support range based header matching for request routing. (#475) v2 api changes: Use oneof to specify header match options, based on value(exact_match), regex or range. The existing value and regex fields will be deprecated. Use the header_match_specfier oneof instead. Add a new range.proto (envoy.type.v2) for the range type definition. The SInt64Range message is defined in envoy.type.v2 range.proto. It consists of start and end (inclusive, exclusive) sint64 values. v1 api: Add a range_match object to the route headers json. Presence of this object indicates range based route match. Example: For the below route config: { "prefix": "/", "cluster": "PartitionB", "name": "PartitionKey", "range_match": { "start": 0, "end": 10} } In the incoming request, if the PartitionKey header value = 0, route match succeeds. Route match fails if the header value = 10, -10, "somestring". This feature can be used for request routing with Service Fabric stateful services, to route to the desired partition with the [ranged partitioning scheme](https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-concepts-partitioning#ranged-partitioning-scheme) Signed-off-by: Kavya Kotacherry <kavyako@microsoft.com>
7 years ago
"//envoy/type:range",
rbac: add metadata support to rbac filter (#3638) Signed-off-by: Yangmin Zhu <ymzhu@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 9e7a3ab6fdf4c55557c3a06a6f7f1fa9c7a4ad7e
7 years ago
"//envoy/type/matcher:metadata",
"//envoy/type/matcher:number",
"//envoy/type/matcher:string",
Move envoy.api.v2 core protos to envoy.api.v2.core and organize filters (#452) There are several main changes in this PR: Create envoy.api.v2.core packages to break circular dependencies from xDS on to subpackages on to base protos. Create individual packages for each filter and add independent versioning to each filter. Add visibility constraints to prevent formation of dependency cycles. Add gogoproto annotations to improve go code generation. After moving xDS service definitions and top-level resource protos back to envoy.core.api.v2, cycles were created, since the second-level definitions depend on base protobuf definitions, and are in turn included from xDS; however xDS and base definitions are in the same package. The solution is to split the base protos into another package, envoy.api.v2.core. That eliminates dependency cycles (validated using go-control-plane). Added a few gogoproto annotations to improve golang code generation. Signed-off-by: Kuat Yessenov <kuat@google.com>
7 years ago
],
)