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.
1663 Commits
2 Branches
0 Tags
17 MiB
Tag: Branch: Tree: 1673512073
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '1673512073'
${ noResults }
data-plane-api/BUILD

296 lines
15 KiB
Raw Normal View History Unescape

Fix proto_sync.py (#12434) Fix path in proto_sync.py generated comments and regenerate. Signed-off-by: wzshiming <wzshiming@foxmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 8c1ad4cb9e0617d43b325a47b6785ea4b57ae475
4 years ago
# DO NOT EDIT. This file is generated by tools/proto_format/proto_sync.py.
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
load("@rules_proto//proto:defs.bzl", "proto_library")
licenses(["notice"]) # Apache 2
proto_library(
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
name = "v2_protos",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
visibility = ["//visibility:public"],
deps = [
"//envoy/admin/v2alpha:pkg",
"//envoy/api/v2:pkg",
"//envoy/api/v2/auth:pkg",
"//envoy/api/v2/cluster:pkg",
"//envoy/api/v2/core:pkg",
"//envoy/api/v2/endpoint:pkg",
"//envoy/api/v2/listener:pkg",
"//envoy/api/v2/ratelimit:pkg",
"//envoy/api/v2/route:pkg",
"//envoy/config/accesslog/v2:pkg",
"//envoy/config/bootstrap/v2:pkg",
"//envoy/config/cluster/aggregate/v2alpha:pkg",
"//envoy/config/cluster/dynamic_forward_proxy/v2alpha:pkg",
"//envoy/config/cluster/redis:pkg",
"//envoy/config/common/dynamic_forward_proxy/v2alpha:pkg",
"//envoy/config/common/tap/v2alpha:pkg",
"//envoy/config/filter/accesslog/v2:pkg",
"//envoy/config/filter/dubbo/router/v2alpha1:pkg",
"//envoy/config/filter/fault/v2:pkg",
"//envoy/config/filter/http/adaptive_concurrency/v2alpha:pkg",
filter: AWS Lambda filter (initial version) (#10260) This filter transform HTTP requests to AWS Lambda invocations. The filter supports pass-through only. Meaning, the request body is passed to Lambda as is. Note: Lambda requires the request to be in JSON format. In a later iteration, we'll wrap the headers the body in a JSON string before passing it to Lambda. The filter requires the ARN of the Lambda function and supports per-filter-config. When the per-filter configuration is used, the target cluster must be tagged with specific metadata. This indicates to the filter whether to process the request or to skip it. Lambda supports two invocation modes: - Synchronous (Request-Response) - Asynchronous (Event) This initial version of the filter supports the synchronous mode only. In a later iteration I'll add support for the asynchronous (Event-based) version. Signed-off-by: Marco Magdy <mmagdy@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 807401004d500899e9aa4c78fce007cf83b538cd
5 years ago
"//envoy/config/filter/http/aws_lambda/v2alpha:pkg",
Add AWS request signing filter (#9751) This new alpha filter injects authentication headers for requests directed at AWS services that require authentication. Note: Requests over plain HTTP aren't handled yet, since the message body needs to be signed. Fixes #9708 Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ ee2306673b79215641be02893cb4d8b2b256c466
5 years ago
"//envoy/config/filter/http/aws_request_signing/v2alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/buffer/v2:pkg",
filter: Add CacheFilter config API (#9960) Signed-off-by: Todd Greer <tgreer@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 77678438d9499bdfd32f0cbe7d2042e72fde4319
5 years ago
"//envoy/config/filter/http/cache/v2alpha:pkg",
filters: add generic compressor filter (#7057) Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 884bc7d13c06ca5c6f59e35ed0a8726b474e1d38
5 years ago
"//envoy/config/filter/http/compressor/v2:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/http/cors/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/csrf/v2:pkg",
"//envoy/config/filter/http/dynamic_forward_proxy/v2alpha:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/http/dynamo/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/ext_authz/v2:pkg",
"//envoy/config/filter/http/fault/v2:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/http/grpc_http1_bridge/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/grpc_http1_reverse_bridge/v2alpha1:pkg",
"//envoy/config/filter/http/grpc_stats/v2alpha:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/http/grpc_web/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/gzip/v2:pkg",
"//envoy/config/filter/http/header_to_metadata/v2:pkg",
"//envoy/config/filter/http/health_check/v2:pkg",
"//envoy/config/filter/http/ip_tagging/v2:pkg",
"//envoy/config/filter/http/jwt_authn/v2alpha:pkg",
"//envoy/config/filter/http/lua/v2:pkg",
On-demand VHDS implementation (#8617) Implements on-demand resolution of VirtualHosts via VHDS Signed-off-by: Dmitri Dolguikh <ddolguik@redhat.com> Mirrored from https://github.com/envoyproxy/envoy @ 8e2d909ad22f84d9eb055f06890924a5879bad76
5 years ago
"//envoy/config/filter/http/on_demand/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/http/original_src/v2alpha1:pkg",
"//envoy/config/filter/http/rate_limit/v2:pkg",
"//envoy/config/filter/http/rbac/v2:pkg",
"//envoy/config/filter/http/router/v2:pkg",
"//envoy/config/filter/http/squash/v2:pkg",
"//envoy/config/filter/http/tap/v2alpha:pkg",
"//envoy/config/filter/http/transcoder/v2:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/listener/http_inspector/v2:pkg",
"//envoy/config/filter/listener/original_dst/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/listener/original_src/v2alpha1:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/listener/proxy_protocol/v2:pkg",
"//envoy/config/filter/listener/tls_inspector/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/client_ssl_auth/v2:pkg",
network: add direct response network filter (#10210) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e8e20c3b045dcde43aee2f7eea63aa0d2b1edb2f
5 years ago
"//envoy/config/filter/network/direct_response/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/dubbo_proxy/v2alpha1:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/network/echo/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/ext_authz/v2:pkg",
"//envoy/config/filter/network/http_connection_manager/v2:pkg",
Kafka: Add broker-level metrics-collecting filter (#8188) Signed-off-by: Adam Kotwasinski <adam.kotwasinski@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ a60f6853a2c2ebbbfed79dfff0b5b644fd735980
5 years ago
"//envoy/config/filter/network/kafka_broker/v2alpha1:pkg",
rate limit: add local rate limit network filter (#9354) Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 9b3915d57ffc280eccab30c34f58926ade5a984e
5 years ago
"//envoy/config/filter/network/local_rate_limit/v2alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/mongo_proxy/v2:pkg",
"//envoy/config/filter/network/mysql_proxy/v1alpha1:pkg",
"//envoy/config/filter/network/rate_limit/v2:pkg",
"//envoy/config/filter/network/rbac/v2:pkg",
"//envoy/config/filter/network/redis_proxy/v2:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/filter/network/sni_cluster/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/filter/network/tcp_proxy/v2:pkg",
"//envoy/config/filter/network/thrift_proxy/v2alpha1:pkg",
"//envoy/config/filter/network/zookeeper_proxy/v1alpha1:pkg",
"//envoy/config/filter/thrift/rate_limit/v2alpha1:pkg",
"//envoy/config/filter/thrift/router/v2alpha1:pkg",
"//envoy/config/filter/udp/udp_proxy/v2alpha:pkg",
"//envoy/config/grpc_credential/v2alpha:pkg",
"//envoy/config/health_checker/redis/v2:pkg",
"//envoy/config/listener/v2:pkg",
"//envoy/config/metrics/v2:pkg",
"//envoy/config/overload/v2alpha:pkg",
"//envoy/config/ratelimit/v2:pkg",
"//envoy/config/rbac/v2:pkg",
"//envoy/config/resource_monitor/fixed_heap/v2alpha:pkg",
"//envoy/config/resource_monitor/injected_resource/v2alpha:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/retry/omit_canary_hosts/v2:pkg",
retry host predicate: add new predicate to omit hosts based on endpoint metadata match (#9563) Currently supported retry host predicates only allow omitting either previously tried or canary hosts. This enhancement is to add a new host predicate that looks at the endpoint metadata match and omits the host in case of a match with the host metadata. See #9531 Risk Level: Low Testing: Unit testing Docs Changes: Added new proto for omit_hosts Signed-off-by: Prakhar Gautam <prakhag@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ e2fdf70f0fca0f9a9a66046fd80b280981b3f0ed
5 years ago
"//envoy/config/retry/omit_host_metadata/v2:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/retry/previous_hosts/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/retry/previous_priorities:pkg",
"//envoy/config/trace/v2:pkg",
"//envoy/config/trace/v2alpha:pkg",
"//envoy/config/transport_socket/alts/v2alpha:pkg",
xds: define empty config protos (#9581) Define empty config protos for all filters expecting google::protobuf::Empty Risk Level: medium (change of config type) Testing: unit Docs Changes: done Release Notes: define config protos for all extensions Co-authored-by: Derek Argueta <dereka@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 2d5a4e94720cc195324f79ca68f0e7a7dc83ee9e
5 years ago
"//envoy/config/transport_socket/raw_buffer/v2:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/config/transport_socket/tap/v2alpha:pkg",
"//envoy/data/accesslog/v2:pkg",
"//envoy/data/cluster/v2alpha:pkg",
"//envoy/data/core/v2alpha:pkg",
dns_filter: Initial commit for dns_filter skeleton (#10376) This commit is this base structure and api definition for the DNS filter. The code itself takes no action on packets. Tests will be added later. Signed-off-by: Alvin Baptiste <alvinsb@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ b3949eaf2080809b8a3a6cf720eba2cfdf864472
5 years ago
"//envoy/data/dns/v2alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
"//envoy/data/tap/v2alpha:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/service/accesslog/v2:pkg",
"//envoy/service/auth/v2:pkg",
"//envoy/service/discovery/v2:pkg",
API definitions for health check & outlier detection event services (#10407) This PR introduces gRPC services interfaces for outlier detection and healthcheck events services. Risk Level: low Testing: n.a. Docs Changes: not yet Release Notes: not yet Relates to #8970 Signed-off-by: Alexey Baranov <me@kotiki.cc> Mirrored from https://github.com/envoyproxy/envoy @ 34fcdef99633947543070d5eadf32867e940694e
5 years ago
"//envoy/service/event_reporting/v2alpha:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/service/load_stats/v2:pkg",
"//envoy/service/metrics/v2:pkg",
"//envoy/service/ratelimit/v2:pkg",
Add Client Status Discovery Service (CSDS) API definition (#9383) Add Client Status Discovery Service (CSDS) API definition. This can be used by debug tools to obtain config information for specific clients from control plane. Risk Level: Low Testing: N/A Signed-off-by: Fuqiang Gao <fuqianggao@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 10f756efa17e56c8d4d1033be7b4286410db4e01
5 years ago
"//envoy/service/status/v2:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/service/tap/v2alpha:pkg",
"//envoy/service/trace/v2:pkg",
"//envoy/type:pkg",
"//envoy/type/matcher:pkg",
"//envoy/type/metadata/v2:pkg",
"//envoy/type/tracing/v2:pkg",
],
)
proto_library(
name = "v3_protos",
visibility = ["//visibility:public"],
deps = [
"//envoy/admin/v3:pkg",
"//envoy/config/accesslog/v3:pkg",
"//envoy/config/bootstrap/v3:pkg",
"//envoy/config/cluster/v3:pkg",
tap: factor out the TAP filter matcher for later reuse in other filters (#12429) This is the 1st PR for #11832 that factors out the TAP filter matcher to prepare for reuse in other filters. Signed-off-by: Yangmin Zhu <ymzhu@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 520389e677cdcd4a85df769deb40f6cdd2f4f6f8
4 years ago
"//envoy/config/common/matcher/v3:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/core/v3:pkg",
"//envoy/config/endpoint/v3:pkg",
"//envoy/config/filter/thrift/router/v2alpha1:pkg",
"//envoy/config/grpc_credential/v3:pkg",
"//envoy/config/health_checker/redis/v2:pkg",
"//envoy/config/listener/v3:pkg",
"//envoy/config/metrics/v3:pkg",
"//envoy/config/overload/v3:pkg",
"//envoy/config/ratelimit/v3:pkg",
"//envoy/config/rbac/v3:pkg",
"//envoy/config/resource_monitor/fixed_heap/v2alpha:pkg",
"//envoy/config/resource_monitor/injected_resource/v2alpha:pkg",
"//envoy/config/retry/omit_canary_hosts/v2:pkg",
v3 packages updates for omit_canary_hosts proto (#14117) Risk Level: LOW Testing: unit ( proto_format and docs ) part of #12841 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c15193642432291f13c6358ed8c4850fba3a8969
4 years ago
"//envoy/config/retry/omit_canary_hosts/v3:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/config/retry/previous_hosts/v2:pkg",
"//envoy/config/route/v3:pkg",
"//envoy/config/tap/v3:pkg",
"//envoy/config/trace/v3:pkg",
"//envoy/data/accesslog/v3:pkg",
"//envoy/data/cluster/v3:pkg",
"//envoy/data/core/v3:pkg",
dns_filter: Initial commit for dns_filter skeleton (#10376) This commit is this base structure and api definition for the DNS filter. The code itself takes no action on packets. Tests will be added later. Signed-off-by: Alvin Baptiste <alvinsb@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ b3949eaf2080809b8a3a6cf720eba2cfdf864472
5 years ago
"//envoy/data/dns/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/data/tap/v3:pkg",
"//envoy/extensions/access_loggers/file/v3:pkg",
"//envoy/extensions/access_loggers/grpc/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/access_loggers/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/clusters/aggregate/v3:pkg",
"//envoy/extensions/clusters/dynamic_forward_proxy/v3:pkg",
"//envoy/extensions/clusters/redis/v3:pkg",
"//envoy/extensions/common/dynamic_forward_proxy/v3:pkg",
http: add support for skip filter match action (#14275) Adds support for associating a match tree with a HTTP filter, supporting a single "Skip" operation that will have the FM ignore the filter for the duration of the stream once matched. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 935a6598cd01324f03608ca77ebffc9608f7af81
4 years ago
"//envoy/extensions/common/matching/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/common/ratelimit/v3:pkg",
"//envoy/extensions/common/tap/v3:pkg",
compressor: expose generic compressor filter to users (#10553) Currently the generic HTTP compressor filter isn't exposed to users even though it's used internally by `envoy.filters.http.gzip` and can be used by external filter extensions. Expose the compressor's config API to users. For example the filter can be configured as follows: ... filter_chains: filters: - name: envoy.http_connection_manager config: http_filters: - name: envoy.filters.http.compressor config: disable_on_etag_header: true content_length: 100 content_type: - text/html - application/json compressor_library: name: envoy.filters.http.compressor.gzip config: memory_level: 3 window_bits: 10 compression_level: best compression_strategy: rle ... Multiple compressor filters using different compressor libraries, e.g. gzip and brotli, can be stacked in one filter chain. Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 49efb9841a58ebdc43a666f55c445911c8e4181c
5 years ago
"//envoy/extensions/compression/gzip/compressor/v3:pkg",
compression: create a decompressor extensibility point and move gzip decompressor (#10744) creates decompressors as an extension point and moves the zlib based gzip decompressor. Signed-off-by: Jose Nino <jnino@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 520e0c7050564ac7886129a87290e9e433470efd
5 years ago
"//envoy/extensions/compression/gzip/decompressor/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/common/fault/v3:pkg",
http: add support for skip filter match action (#14275) Adds support for associating a match tree with a HTTP filter, supporting a single "Skip" operation that will have the FM ignore the filter for the duration of the stream once matched. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 935a6598cd01324f03608ca77ebffc9608f7af81
4 years ago
"//envoy/extensions/filters/common/matcher/action/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/adaptive_concurrency/v3:pkg",
admission control: Filter implementation with no-op controller (#11414) Signed-off-by: Tony Allen <tony@allen.gg> Mirrored from https://github.com/envoyproxy/envoy @ 83433aea3d9959f866c1794a33e08270c6083094
5 years ago
"//envoy/extensions/filters/http/admission_control/v3alpha:pkg",
filter: AWS Lambda filter (initial version) (#10260) This filter transform HTTP requests to AWS Lambda invocations. The filter supports pass-through only. Meaning, the request body is passed to Lambda as is. Note: Lambda requires the request to be in JSON format. In a later iteration, we'll wrap the headers the body in a JSON string before passing it to Lambda. The filter requires the ARN of the Lambda function and supports per-filter-config. When the per-filter configuration is used, the target cluster must be tagged with specific metadata. This indicates to the filter whether to process the request or to skip it. Lambda supports two invocation modes: - Synchronous (Request-Response) - Asynchronous (Event) This initial version of the filter supports the synchronous mode only. In a later iteration I'll add support for the asynchronous (Event-based) version. Signed-off-by: Marco Magdy <mmagdy@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 807401004d500899e9aa4c78fce007cf83b538cd
5 years ago
"//envoy/extensions/filters/http/aws_lambda/v3:pkg",
Add AWS request signing filter (#9751) This new alpha filter injects authentication headers for requests directed at AWS services that require authentication. Note: Requests over plain HTTP aren't handled yet, since the message body needs to be signed. Fixes #9708 Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ ee2306673b79215641be02893cb4d8b2b256c466
5 years ago
"//envoy/extensions/filters/http/aws_request_signing/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/buffer/v3:pkg",
filter: Add CacheFilter config API (#9960) Signed-off-by: Todd Greer <tgreer@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 77678438d9499bdfd32f0cbe7d2042e72fde4319
5 years ago
"//envoy/extensions/filters/http/cache/v3alpha:pkg",
http: add CDN-Loop header filter (#13158) The CdnLoopFilter implements an HTTP filter that detects and prevents CDN loops using the RFC 8586 CDN-Loop header. The filter can be configured with the CDN identifier to look for as well as the number of times the CDN identifier can be seen before responding with an error. Signed-off-by: Justin Mazzola Paluska <justinmp@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c71ec2729cc3c0708223d303e0f24e3bf9a5d0eb
4 years ago
"//envoy/extensions/filters/http/cdn_loop/v3alpha:pkg",
filters: add generic compressor filter (#7057) Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@linux.intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 884bc7d13c06ca5c6f59e35ed0a8726b474e1d38
5 years ago
"//envoy/extensions/filters/http/compressor/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/cors/v3:pkg",
"//envoy/extensions/filters/http/csrf/v3:pkg",
compression: add generic decompressor filter (#11172) Commit Message: add generic decompressor filter Risk Level: low - low as it is an extension, med - for users as this is a brand new filter. Testing: unit tests, integration tests Docs Changes: added docs Release Notes: added release notes Signed-off-by: Jose Nino <jnino@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 48a5b21d9483e7eddac79aeff7daac178d7b7462
5 years ago
"//envoy/extensions/filters/http/decompressor/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/dynamic_forward_proxy/v3:pkg",
"//envoy/extensions/filters/http/dynamo/v3:pkg",
"//envoy/extensions/filters/http/ext_authz/v3:pkg",
External processing filter protos (#13893) This introduces a new filter called the "external processing filter." It is intended to allow an external service to be able to operate as if it were part of the filter chain using a gRPC stream. It is intended to support a variety of use cases in which processing of HTTP requests and responses by an external service is desired. A document that describes the filter can be found here: https://docs.google.com/document/d/1IZqm5IUnG9gc2VqwGaN5C2TZAD9_QbsY9Vvy5vr9Zmw/edit#heading=h.3zlthggr9vvv Signed-off-by: Gregory Brail <gregbrail@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 98d2f3b553b87c3e935f57ba15b4faf68b45d7f0
4 years ago
"//envoy/extensions/filters/http/ext_proc/v3alpha:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/fault/v3:pkg",
"//envoy/extensions/filters/http/grpc_http1_bridge/v3:pkg",
"//envoy/extensions/filters/http/grpc_http1_reverse_bridge/v3:pkg",
"//envoy/extensions/filters/http/grpc_json_transcoder/v3:pkg",
"//envoy/extensions/filters/http/grpc_stats/v3:pkg",
"//envoy/extensions/filters/http/grpc_web/v3:pkg",
"//envoy/extensions/filters/http/gzip/v3:pkg",
"//envoy/extensions/filters/http/header_to_metadata/v3:pkg",
"//envoy/extensions/filters/http/health_check/v3:pkg",
"//envoy/extensions/filters/http/ip_tagging/v3:pkg",
"//envoy/extensions/filters/http/jwt_authn/v3:pkg",
http: add Kill Request HTTP filter (#14170) Add a KillRequest HTTP filter which can crash Envoy when receiving a Kill request. It will be used to fault inject kill request to Envoy and measure the blast radius. Risk Level: Low, new feature. Testing: Unit/integration tests. Docs Changes: Added Release Notes: Added Issue: #13978 Signed-off-by: Qin Qin <qqin@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 237b29d6399953f22a47c6e4d19df74b4fbcee8d
4 years ago
"//envoy/extensions/filters/http/kill_request/v3:pkg",
Add HTTP local rate limiter (#13395) Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ 5d12b675fe13747bc716859275c2d3c21004e99f
4 years ago
"//envoy/extensions/filters/http/local_ratelimit/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/lua/v3:pkg",
Add OAuth filter (#11268) This was written by Derek Argueta originally. Some more work might be needed to make it more generic. Risk Level: low, new filter Testing: unit tests included Docs Changes: filter docs added Signed-off-by: Snow Pettersen <snowp@lyft.com> Co-authored-by: Derek Argueta <darguetap@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ c6bfd7f9f52468d576781a9b1fe9ea5d3f9086c9
4 years ago
"//envoy/extensions/filters/http/oauth2/v3alpha:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/http/on_demand/v3:pkg",
"//envoy/extensions/filters/http/original_src/v3:pkg",
"//envoy/extensions/filters/http/ratelimit/v3:pkg",
"//envoy/extensions/filters/http/rbac/v3:pkg",
"//envoy/extensions/filters/http/router/v3:pkg",
"//envoy/extensions/filters/http/squash/v3:pkg",
"//envoy/extensions/filters/http/tap/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/filters/http/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/listener/http_inspector/v3:pkg",
"//envoy/extensions/filters/listener/original_dst/v3:pkg",
"//envoy/extensions/filters/listener/original_src/v3:pkg",
"//envoy/extensions/filters/listener/proxy_protocol/v3:pkg",
"//envoy/extensions/filters/listener/tls_inspector/v3:pkg",
"//envoy/extensions/filters/network/client_ssl_auth/v3:pkg",
network: add direct response network filter (#10210) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e8e20c3b045dcde43aee2f7eea63aa0d2b1edb2f
5 years ago
"//envoy/extensions/filters/network/direct_response/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/dubbo_proxy/router/v3:pkg",
"//envoy/extensions/filters/network/dubbo_proxy/v3:pkg",
"//envoy/extensions/filters/network/echo/v3:pkg",
"//envoy/extensions/filters/network/ext_authz/v3:pkg",
"//envoy/extensions/filters/network/http_connection_manager/v3:pkg",
"//envoy/extensions/filters/network/kafka_broker/v3:pkg",
"//envoy/extensions/filters/network/local_ratelimit/v3:pkg",
"//envoy/extensions/filters/network/mongo_proxy/v3:pkg",
"//envoy/extensions/filters/network/mysql_proxy/v3:pkg",
filter: postgres statistics network filter (#10642) Description: The filter implements decoding postgres wire protocol and parses messages exchanged between postgres server and client. Based on the decoded messages the filter generates statistics (counters) indicating how many messages of a specific type were exchanged. #9107 Risk Level: Low: The filter is implemented as extension and the code is not executed unless inserted into filter chain. Testing: Added unit and integration tests. Docs Changes: Yes - added architecture overview chapter and configuration specific sections Release Notes: Yes Signed-off-by: Christoph Pakulski <christoph@tetrate.io> Co-authored-by: Dhi Aurrahman <dio@tetrate.io> Co-authored-by: Fabrízio de Royes Mello <fabrizio@ongres.com> Mirrored from https://github.com/envoyproxy/envoy @ f599ad7c05824a2cdbcde60ab2c035d264cd4247
5 years ago
"//envoy/extensions/filters/network/postgres_proxy/v3alpha:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/ratelimit/v3:pkg",
"//envoy/extensions/filters/network/rbac/v3:pkg",
"//envoy/extensions/filters/network/redis_proxy/v3:pkg",
rocketmq_proxy: implement rocketmq proxy Implement rocketmq proxy Description: implement rocketmq proxy Risk Level: Low Testing: Unit Tests Docs Changes: N/A Release Notes: N/A Fixes #9431 Signed-off-by: aaron-ai <yangkun.ayk@alibaba-inc.com> Mirrored from https://github.com/envoyproxy/envoy @ 0a7dba7933af7c5e1ffd842d76d221881dd46a24
5 years ago
"//envoy/extensions/filters/network/rocketmq_proxy/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/sni_cluster/v3:pkg",
SNI-based dynamic forward proxy filter (#10448) Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ bc4ea0a8202096b2eadaf17d05bdb7686418d603
5 years ago
"//envoy/extensions/filters/network/sni_dynamic_forward_proxy/v3alpha:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/tcp_proxy/v3:pkg",
"//envoy/extensions/filters/network/thrift_proxy/filters/ratelimit/v3:pkg",
"//envoy/extensions/filters/network/thrift_proxy/v3:pkg",
Upstream Wasm proto from envoy-wasm. (#12159) Description: Upstream Wasm proto files from envoy-wasm. Risk Level: Low Testing: Unit tests in envoy-wasm, integration tests in istio/proxy. Docs Changes: N/A Release Notes: N/A Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 26eaa2e85cee69e5c32ab6bf4c5ae3d338fa462f
4 years ago
"//envoy/extensions/filters/network/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/filters/network/zookeeper_proxy/v3:pkg",
dns_filter: Add request parsing (#10697) This change adds DNS Request Parsing to the DNS filter. The filter will parse and decode DNS requests for A and AAAA records. Tests simply validate that the filter can consume queries. Signed-off-by: Alvin Baptiste <alvinsb@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 54cd4d49e895befb8ecb10ebb14585cd8fc71ee7
5 years ago
"//envoy/extensions/filters/udp/dns_filter/v3alpha:pkg",
udp_proxy: upgrade to not alpha (#11339) This extension is used in production and we should treat it as such. Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 86caf439d6cae2c8173b19fd4fdc95361565a72d
5 years ago
"//envoy/extensions/filters/udp/udp_proxy/v3:pkg",
router: Create InternalRedirectPolicy in side RouteAction and extend it with pluggable predicates (#10908) Description: router: Create InternalRedirectPolicy to capture all internal redirect related options and extend it with pluggable predicates similar to retry plugins. The previous_routes and whitelisted_routes predicate allow creating a DAG of routes for internal redirects. Each node in the DAG is a route. whitelisted_routes defines the edges of each node. previous_routes serves as visited status keeper for each of the edge. This prevents infinite loop, while allowing loop to exist in the DAG. Risk Level: Medium Testing: Unit tests. Integration tests. Docs Changes: Updated HCM architecture overview page. Added toctree for the predicates. Release Notes: Updated version history. Signed-off-by: pengg <pengg@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 1ce010929d4d283fce977bc65558da71ffe6bf7c
5 years ago
"//envoy/extensions/internal_redirect/allow_listed_routes/v3:pkg",
"//envoy/extensions/internal_redirect/previous_routes/v3:pkg",
"//envoy/extensions/internal_redirect/safe_cross_scheme/v3:pkg",
network: add socket interface factory and config option (#11630) Add bootstrap config option that allows startup injection of a custom SocketInterface. Risk Level: Low Testing: n/a Docs Changes: n/a Release Notes: n/a Signed-off-by: Florin Coras <fcoras@cisco.com> Mirrored from https://github.com/envoyproxy/envoy @ 13da8f415c372e7fde3b0105f58f57348e84acb5
4 years ago
"//envoy/extensions/network/socket_interface/v3:pkg",
rate limit: add computed descriptors (#14448) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 876a36368b0617b43977abfc37d2b5af05e7b1b2
4 years ago
"//envoy/extensions/rate_limit_descriptors/expr/v3:pkg",
retry host predicate: add new predicate to omit hosts based on endpoint metadata match (#9563) Currently supported retry host predicates only allow omitting either previously tried or canary hosts. This enhancement is to add a new host predicate that looks at the endpoint metadata match and omits the host in case of a match with the host metadata. See #9531 Risk Level: Low Testing: Unit testing Docs Changes: Added new proto for omit_hosts Signed-off-by: Prakhar Gautam <prakhag@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ e2fdf70f0fca0f9a9a66046fd80b280981b3f0ed
5 years ago
"//envoy/extensions/retry/host/omit_host_metadata/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/retry/priority/previous_priorities/v3:pkg",
Upstream envoyproxy/envoy-wasm. (#12546) Signed-off-by: John Plevyak <jplevyak@gmail.com> Signed-off-by: Piotr Sikora <piotrsikora@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 319a9a647f19036d831a75f68350c90e98bfc365
4 years ago
"//envoy/extensions/stat_sinks/wasm/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/alts/v3:pkg",
transport socket: Add proxy proto transport socket. (#11584) Commit Message: Add proxy proto transport socket Additional Description: This is the part 1 PR described in #10682. It adds the transports socket / unit tests, a transport socket options struct for the proxy proto header, and does a refactor to make the listener filter use the common proxy proto constants (potentially want to move these now since the proxy proto config api type is not in extensions?) Risk Level: Small Testing: Unit Docs Changes: None Release Notes: None Part Of: #1031 Signed-off-by: Weston Carlson <wez470@gmail.com> Co-authored-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 8972b478e6c9f1e7342e3dbfb57b35317c0cc009
4 years ago
"//envoy/extensions/transport_sockets/proxy_protocol/v3:pkg",
quiche: update tar and implement EnvoyQuicProofSource (#11316) Signed-off-by: Dan Zhang <danzh@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 92e608f066b017d664d8fa161cfc735f0c6b41e7
5 years ago
"//envoy/extensions/transport_sockets/quic/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/raw_buffer/v3:pkg",
transport socket: api and implementation for startTls transport socket (#13112) Signed-off-by: Christoph Pakulski <christoph@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 98e8bf3f09fa2af3735217bfc7046517250cdfd2
4 years ago
"//envoy/extensions/transport_sockets/starttls/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/extensions/transport_sockets/tap/v3:pkg",
"//envoy/extensions/transport_sockets/tls/v3:pkg",
upstreams: APIs, docs, and stubs for pluggable upstreams (#11554) split out from #11327 There's a bit of transitive ugliness: declaring the extensions requires security posture, requires stub build files, requires codeowners before the code move, but it'll be pretty short lived. Risk Level: Low (mostly only APIs) Testing: n/a Docs Changes: some of the new docs Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ e8dc25ecec277c0b94d02151de79353a9ba07b4e
5 years ago
"//envoy/extensions/upstreams/http/generic/v3:pkg",
"//envoy/extensions/upstreams/http/http/v3:pkg",
"//envoy/extensions/upstreams/http/tcp/v3:pkg",
config: reworking HTTP upstream config (#14079) Replacing the http-protocol-specific fields in the cluster config with a new plugin Risk Level: medium Testing: updated tests to use the new config Docs Changes: updated docs to use the new config Release Notes: deprecation notes in the PR Deprecated: all http-specific cluster config. Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 7554d61bccf136638bdfb383c10d049dc8bd3790
4 years ago
"//envoy/extensions/upstreams/http/v3:pkg",
conn_pool: making TCP upstreams pluggable (#13548) Risk Level: Medium (some refactory) Testing: existing tests pass Docs Changes: n/a Release Notes: n/a Fixes #13185 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 6a044a38b762214950aea40fcd0709cd7dccdc44
4 years ago
"//envoy/extensions/upstreams/tcp/generic/v3:pkg",
Proxy-WASM configuration protos. (#9256) Signed-off-by: John Plevyak <jplevyak@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ bd637c4e3d691a74721049bba5aacc4551123aa8
5 years ago
"//envoy/extensions/wasm/v3:pkg",
Watchdog Extension: Profile Action (#12636) Added a watchdog extension that triggers profiling. Risk Level: Medium (new extension that is optional) Testing: Unit tests Docs Changes: Included (added a reference to the generated extension proto.rst) Release Notes: Included Fixes #11388 Signed-off-by: Kevin Baichoo <kbaichoo@google.com> Mirrored from https://github.com/envoyproxy/envoy @ c88515fc0c8a291992732947671190b37949bbbd
4 years ago
"//envoy/extensions/watchdog/profile_action/v3alpha:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/accesslog/v3:pkg",
"//envoy/service/auth/v3:pkg",
"//envoy/service/cluster/v3:pkg",
"//envoy/service/discovery/v3:pkg",
"//envoy/service/endpoint/v3:pkg",
API definitions for health check & outlier detection event services (#10407) This PR introduces gRPC services interfaces for outlier detection and healthcheck events services. Risk Level: low Testing: n.a. Docs Changes: not yet Release Notes: not yet Relates to #8970 Signed-off-by: Alexey Baranov <me@kotiki.cc> Mirrored from https://github.com/envoyproxy/envoy @ 34fcdef99633947543070d5eadf32867e940694e
5 years ago
"//envoy/service/event_reporting/v3:pkg",
External processing filter protos (#13893) This introduces a new filter called the "external processing filter." It is intended to allow an external service to be able to operate as if it were part of the filter chain using a gRPC stream. It is intended to support a variety of use cases in which processing of HTTP requests and responses by an external service is desired. A document that describes the filter can be found here: https://docs.google.com/document/d/1IZqm5IUnG9gc2VqwGaN5C2TZAD9_QbsY9Vvy5vr9Zmw/edit#heading=h.3zlthggr9vvv Signed-off-by: Gregory Brail <gregbrail@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 98d2f3b553b87c3e935f57ba15b4faf68b45d7f0
4 years ago
"//envoy/service/ext_proc/v3alpha:pkg",
xds: implement extension config discovery for HCM (#11826) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e8216a8cf79c54e3e0a77ab729ebf27f4e79eb1b
4 years ago
"//envoy/service/extension/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/health/v3:pkg",
"//envoy/service/listener/v3:pkg",
"//envoy/service/load_stats/v3:pkg",
"//envoy/service/metrics/v3:pkg",
"//envoy/service/ratelimit/v3:pkg",
"//envoy/service/route/v3:pkg",
"//envoy/service/runtime/v3:pkg",
"//envoy/service/secret/v3:pkg",
Add Client Status Discovery Service (CSDS) API definition (#9383) Add Client Status Discovery Service (CSDS) API definition. This can be used by debug tools to obtain config information for specific clients from control plane. Risk Level: Low Testing: N/A Signed-off-by: Fuqiang Gao <fuqianggao@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 10f756efa17e56c8d4d1033be7b4286410db4e01
5 years ago
"//envoy/service/status/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/service/tap/v3:pkg",
"//envoy/service/trace/v3:pkg",
"//envoy/type/matcher/v3:pkg",
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
"//envoy/type/metadata/v3:pkg",
"//envoy/type/tracing/v3:pkg",
api: freeze v3 API. (#9694) In which we convert every v3alpha reference to v3. In future revs of the stable API versioning policy, we will develop better tooling to support > 2 alpha and stable versions. For v3, it seems reasonable to just mv v3alpha to v3, since there should be no external consumers yet. Risk level: Low Testing: bazel test //test/..., CI. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf
5 years ago
"//envoy/type/v3:pkg",
Watchdog: use abort action as a default if killing is enabled. (#13523) Use abort action as a default if killing is enabled and we're on a supported platform. Risk Level: low Testing: unit tests Docs Changes: Included Release Notes: Included See PR #13208 for context as the reason it's part of core envoy and not an extension. Signed-off-by: Kevin Baichoo <kbaichoo@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 415af040e09a1f6993c15ffc022793d39ecf5e8e
4 years ago
"//envoy/watchdog/v3alpha:pkg",
tools: API boosting support for renames. (#9442) The type database now has rename information. Also some misc. fixes for enum and generated static method handling support. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2c8992bce1880ed7ae8ede837434b8713c24a615
5 years ago
],
)
api/docs: v3 API reference documentation. (#9719) This PR introduces a parallel v3 API reference documentation tree to the existing v2 one. The docs/root/api-v3/ tree was copied from docs/root/api-v2 and the necessary package path fixups were made manually. As a result, the tree largely resembles the v2 docs. Long term this is likely to evolve to reflect the shape of the new extensions tree. The message type, field and enum anchors are sed'ed to be distinct and self-consistent inside api-v3/. There were a number of API proto changes that were made to obtain a successful Sphinx build: * References to deprecated fields were replaced by references to the replacement field. * clang-format line wrapping in protoxform was removed, this breaks RST in some v3 protos. * Some packages (type/metadata/v2, data/cluster/v2alpha) were force upgraded to v3, to deal with references to types that are distinct in v2/v3. This is OK as these packages probably make sense to bump for v3, in general we're going to have to think about how to do this more cleanly, supporting dual v2/v3 references alongside each other. * Some evil hacks for field renaming added to migrate.py for RouteAction. There's also some additional machinery added to compute distinct v3/v3 build targets to point protodoc at. Risk level: Low Testing: Docs build, manual inspection. Fixes #8087 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ac88316892cd47b6a9b58e3736e20e8863cd0d27
5 years ago
proto_library(
name = "all_protos",
visibility = ["//visibility:public"],
deps = [
":v2_protos",
":v3_protos",
],
)