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

304 lines
16 KiB
Raw Normal View History Unescape

api/tools: some progress towards generalizing API version upgrade. (#10507) * Automatically derive active protos target used in proto_format.sh from the packages with files annotated as active. * Replace some sites with hardcoded v2/v3 with active/next_major_version_candidate. * Move //docs:BUILD to //versioning:BUILD in API tree. This has already ceased to be used directly in the docs build, so this makes things a bit clearer. Risk level: Low (API tooling and build only) Testing: fix_format (mostly idempotent) Part of #10355. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4403003b9c0888ce81606a2f45fcc1da126514e7
5 years ago
# DO NOT EDIT. This file is generated by tools/proto_format/active_protos_gen.py.
rename packages (#9515) Description: Move packages around for #8120 and #8121 Risk Level: Med around messing up build. Testing: CI Docs Changes: in API/STYLE.md Release Notes: N/A (v3alpha is not in use yet) Fixes #8120 Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 1371f2ef46582a72b5b3971147bd87c534011731
5 years ago
load("@rules_proto//proto:defs.bzl", "proto_library")
build: use rules_cc and use buildifier -lint to enforce it (#11399) Commit Message: Partially address #9488. Resurrected #10597. Additional Description: Risk Level: Low Testing: CI Docs Changes: N/A Release Notes: N/A Signed-off-by: Lizan Zhou <lizan@tetrate.io> Mirrored from https://github.com/envoyproxy/envoy @ 67649af8d4881fb7593c728f181eff393f85a638
5 years ago
licenses(["notice"]) # Apache 2
api: tools/docs to support v2 freeze, v4alpha cut. (#10636) This patch introduces the tools/docs for a new flow for protoxform: freeze. This performs a major version freeze and bump by modifying package_version_status. Tooling now needs to deal with 3 possible versions (v2, v3, v4alpha). The following contributions are made in the patch: * Tooling added to support v2 APIs freeze, transitioning v3 to active and generating v4alpha. * A new tool, merge_active_shadow.py, is introduced to combine hand-edited active v3 API protos with the v2 implied shadows for deprecated fields. * The type database now spans v2 and v3 (and implied v4alpha files) * api_proto_plugins can now take extra args on the Bazel CLI; this is used to plumb in the freeze arg to protoxform. Docs are updated to reflect the v3 flow that developers should now follow. Part of #10355 This is the tools/docs component of #10601. See #10601 for the resulting API protos generated by a freeze/fix cycle. Risk level: Low (tooling only, no API changes yet) Testing: new golden protos tests for protoxform, unit tests for merge_active_shadow. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ de222c3acf1fbf124ca44f50495fc4b8e9aba525
5 years ago
# This tracks active development versions of protos.
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
proto_library(
api/tools: some progress towards generalizing API version upgrade. (#10507) * Automatically derive active protos target used in proto_format.sh from the packages with files annotated as active. * Replace some sites with hardcoded v2/v3 with active/next_major_version_candidate. * Move //docs:BUILD to //versioning:BUILD in API tree. This has already ceased to be used directly in the docs build, so this makes things a bit clearer. Risk level: Low (API tooling and build only) Testing: fix_format (mostly idempotent) Part of #10355. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4403003b9c0888ce81606a2f45fcc1da126514e7
5 years ago
name = "active_protos",
tools: api_booster tool for upgrading Envoy APIs (tool only) (#9329) This is a beachhead PR for a Clang Libtooling based workflow that automagically updates Envoy's source tree to the latest API version for every referenced package. So far, ths tool is only capable of inferring types and performing header fixups, later PRs will expand this. Risk level: Low Testing: Manual cleanup of all headers in source/ test/ and include/, all tests pass. Part of #8082 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ b54d1c366744314dda38aed5f14e7e93323acb41
5 years ago
visibility = ["//visibility:public"],
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
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: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
"//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",
"//envoy/data/dns/v3:pkg",
"//envoy/data/tap/v3:pkg",
"//envoy/extensions/access_loggers/file/v3:pkg",
"//envoy/extensions/access_loggers/grpc/v3:pkg",
Add an OpenTelemetry (gRPC) access logger extension (#15105) This PR adds an OTLP logger to Envoy, which allows users to flexibly configure their log structure (according to OpenTelemetry protos). The API users the common gRPC configuration, used in ALS, for gRPC settings. The flexible OT fields (body, attributes) are completely configurable and are filled with request/response information based on Envoy access log formatting. There are still a couple of TODOs - The 'filter_state_objects_to_log' from the common gRPC config isn't added to the log Resource attributes are not configurable, and only Envoy node info is added. Note: this extension was added as v3alpha API. Risk Level: Low - a new extension, so unlikely to break any existing setups (marked as v3alpha API). Testing: Unit tests. Docs Changes: Release Notes: access log: added a new :ref:OpenTelemetry access logger <envoy_v3_api_msg_extensions.access_loggers.open_telemetry.v3alpha.OpenTelemetryAccessLogConfig> extension, allowing a flexible log structure with native Envoy access log formatting. Signed-off-by: Itamar Kaminski <itamark@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4f52f9ef554e1522e763c0eaf6ef6833aab283e5
4 years ago
"//envoy/extensions/access_loggers/open_telemetry/v3alpha:pkg",
Rename access log streams to make it more friendly to posix terminology (#15721) Signed-off-by: Sotiris Nanopoulos <sonanopo@microsoft.com> Mirrored from https://github.com/envoyproxy/envoy @ 98fb5d6f8fe09a88218598d757756e702857dd03
4 years ago
"//envoy/extensions/access_loggers/stream/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",
protos: Move simple_http_cache config proto to api (#16230) Signed-off-by: Ryan Northey <ryan@synca.io> Mirrored from https://github.com/envoyproxy/envoy @ dede3aace85684d732758dab02806f773bd56846
4 years ago
"//envoy/extensions/cache/simple_http_cache/v3alpha:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/common/ratelimit/v3:pkg",
"//envoy/extensions/common/tap/v3:pkg",
compression: add brotli compressor and decompressor (#12998) Commit Message: compression: add brotli compressor and decompressor Additional Description: Add new brotli compression extensions in addition to gzip. Risk Level: Low, no existing functionality is touched Testing: uni tests, manual tests with curl. Docs Changes: updated docs for compression and decompression HTTP filters to refer the new available encoder/decoder. Release Notes: updated current.rst Fixes #4429 The PR adds a new dependency on https://github.com/google/brotli. Here's the current criteria answers: | Criteria | Answer | |---------|---------| | Cloud Native Computing Foundation (CNCF) approved license | MIT | | Dependencies must not substantially increase the binary size unless they are optional | brotli's binary size built with `-c opt` is 752K | | No duplication of existing dependencies | no other dep provides Brotli | | Hosted on a git repository and the archive fetch must directly reference this repository. | https://github.com/google/brotli | | CVE history appears reasonable, no pathological CVE arcs | so far 4 CVEs related to brotli have been registered | | Code review (ideally PRs) before merge | PRs are reviewed before merge | | Security vulnerability process exists, with contact details and reporting/disclosure process | no policy exists, submitted https://github.com/google/brotli/issues/878 | | > 1 contributor responsible for a non-trivial number of commits | 75 contributors | | Tests run in CI | CI set up with AppVeyor and Github actions | | High test coverage (also static/dynamic analysis, fuzzing) | Fuzzers are run in CI | | Envoy can obtain advanced notification of vulnerabilities or of security releases | brotli is registered in CPE | | Do other significant projects have shared fate by using this dependency? | Google Chrome is using the library | | Releases (with release notes) | https://github.com/google/brotli/releases | | Commits/releases in last 90 days | last commit 9 days ago | Signed-off-by: Dmitry Rozhkov <dmitry.rozhkov@intel.com> Mirrored from https://github.com/envoyproxy/envoy @ 127aa55306c9e4366e10b3a6e26d01df826e2fc0
4 years ago
"//envoy/extensions/compression/brotli/compressor/v3:pkg",
"//envoy/extensions/compression/brotli/decompressor/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",
filters: Add dependencies.proto (#14750) Introduces the FilterDependency proto. This isn't quite an extension, but it's a common proto to be used by all filter extensions. Risk Level: Low (proto addition only) #14470 Signed-off-by: Auni Ahsan <auni@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 2da224f88afe5ec84ba802bd932f73ed13308a92
4 years ago
"//envoy/extensions/filters/common/dependency/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/filters/http/aws_lambda/v3:pkg",
"//envoy/extensions/filters/http/aws_request_signing/v3:pkg",
"//envoy/extensions/filters/http/buffer/v3:pkg",
"//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",
http: add composite filter allowing dynamic filter selection (#15198) Adds a new filter that makes use of the new matching API to allow specifying a filter configuration to use for specific match results. Once a configuration is selected, the desired filter is created and all callbacks delegated to the specific filter. Risk Level: Low, new filter Testing: IT + UT Docs Changes: Inline proto comments Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ d31ba23d494c310973ceaf1e053393697821e4d3
4 years ago
"//envoy/extensions/filters/http/composite/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/filters/http/compressor/v3:pkg",
"//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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
Set-Metadata HTTP filter (#16400) This extension simply allows to add user-defined dynamic metadata. This is intended to be used with matchers, so that the "result" of a matching process can imply specific metadata. See issue #16266 Risk Level: Medium Testing: Unit tests for the extension are added Docs Changes: A small documentation for the extension is added in docs/root/configuration/http/http_filters Signed-off-by: Adrien Guinet <adrien@reblaze.com> Mirrored from https://github.com/envoyproxy/envoy @ cbe08bbe33005c1832964f7c9e657d6dbe105bbb
4 years ago
"//envoy/extensions/filters/http/set_metadata/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
"//envoy/extensions/filters/network/direct_response/v3:pkg",
"//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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/filters/network/tcp_proxy/v3:pkg",
"//envoy/extensions/filters/network/thrift_proxy/filters/ratelimit/v3:pkg",
Migrate v2 thrift_filter to v3 api and corresponding docs changes. (#13885) part of #12841 Signed-off-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ 77d7cecb7e68cb41b2f5f7c2aa7f4294c88089ce
4 years ago
"//envoy/extensions/filters/network/thrift_proxy/router/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/health_checkers/redis/v3:pkg",
http: add HTTP/1.1 case preservation (#15619) 1) Add new stateful header formatter extension point 2) Add preserve case formatter extension Fixes https://github.com/envoyproxy/envoy/issues/14363 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 2a4d97ce66db565d191b42cdf51f4b99edf04f12
4 years ago
"//envoy/extensions/http/header_formatters/preserve_case/v3:pkg",
HCM: add support for IP detection extensions (#14855) This is a follow-up to: #14432 (comment) After that PR, it's no longer possible (unless you do a dynamic_cast) to set the remote address from a filter. This is something that we need to do because we have specialized logic for this (XFF doesn't work for us). So this adds an extension point which will allow us to push that logic down to ConnectionManagerUtility::mutateRequestHeaders() where it belongs. Signed-off-by: Raul Gutierrez Segales <rgs@pinterest.com> Mirrored from https://github.com/envoyproxy/envoy @ beac1ece7512e6e39b4f1c29490e247996a0f51c
4 years ago
"//envoy/extensions/http/original_ip_detection/custom_header/v3:pkg",
"//envoy/extensions/http/original_ip_detection/xff/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",
matching: add support for generic inputs and add environment variable input (#15410) Adds support for a "generic input" extension point that allows specifying inputs that are not dependent on protocol data. Adds an environment variable generic input that allows matching on the value of an environment variable. Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 758a9a90c15331fbfd093f23170454c5a2fbf903
4 years ago
"//envoy/extensions/matching/common_inputs/environment_variable/v3:pkg",
matching: introduce consistent hashing matcher (#14875) This introduces a new matcher that allows matching on an input value by computing a hash value and matching if the value % (configured value) is greater than a configured threshold. This is useful in being able to define match criteria that should match for a certain % of input values in a way that is consistent between independent Envoy instances (e.g. it does not rely on a random input). Risk Level: Low, new extension Testing: UTs Docs Changes: Inline proto docs Release Notes: n/a Platform Specific Features: n/a Fixes #14782 Signed-off-by: Snow Pettersen <snowp@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 7fe3d358f7e7e4d4c7282d50c498a7ab0e759a36
4 years ago
"//envoy/extensions/matching/input_matchers/consistent_hashing/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",
request_id: allow disabling trace reason packing (#15248) 1) Promote the default UUID request_id implementation to an actual extension that is required in the build and wire up all documentation. 2) Add a configuration option to the extension that allows trace reason packing to be disabled (the default continues to be for it to be enabled to match existing behavior). 3) Update all documentation for the new behavior. 4) Substantial cleanup of these code paths for clarity and robustness. Fixes https://github.com/envoyproxy/envoy/issues/11532 Signed-off-by: Matt Klein <mklein@lyft.com> Mirrored from https://github.com/envoyproxy/envoy @ 07c4c17be61c77d87d2c108b0775f2e606a7ae12
4 years ago
"//envoy/extensions/request_id/uuid/v3:pkg",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/resource_monitors/fixed_heap/v3:pkg",
"//envoy/extensions/resource_monitors/injected_resource/v3:pkg",
"//envoy/extensions/retry/host/omit_canary_hosts/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/retry/host/omit_host_metadata/v3:pkg",
extensions: update straggler v2 extensions to v3. (#14907) * Add v3 equivalents of v2 configs that were included in v3 due to no transitive deprecation. This increases consistency and reduces user confusion. We will continue to support these straggler v2 configs beyond the v2 turndown due to the late addition of v3 counterparts, special case code is added to utility.cc to handle this. * There were two extensions, //envoy/config/cluster/redis and //envoy/config/retry/previous_priorities, that for some reason were not upgraded to use v3 config. This is now fixed and I've grepped for other v2 in //source, none remain. Risk level: Medium (changes to extension config types and deprecated config handling). Testing: Additional unit test added for utility.cc handling, upgraded configs to v3 for other tests. Fixes #14735 Fixes #12841 Signed-off-by: Harvey Tuch <htuch@google.com> Co-authored-by: Abhay Narayan Katare <abhay.katare@india.nec.com> Mirrored from https://github.com/envoyproxy/envoy @ c04a75efe9d601ebcb9650f274b5adde60181f1c
4 years ago
"//envoy/extensions/retry/host/previous_hosts/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/extensions/transport_sockets/raw_buffer/v3:pkg",
Config proto for Secure Session Agent (S2A) transport socket extension. (#16183) Config proto for Secure Session Agent (S2A) transport socket extension (#16110). Signed-off-by: Tavish Vaidya <tavish@google.com> Mirrored from https://github.com/envoyproxy/envoy @ abe2f9b4af4b3c697ee8b3fda934aa2e181bc5ef
4 years ago
"//envoy/extensions/transport_sockets/s2a/v3alpha: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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
"//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 of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
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",
"//envoy/service/status/v3:pkg",
"//envoy/service/tap/v3:pkg",
"//envoy/service/trace/v3:pkg",
[http] API changes to split path header normalization and forwarding (#15044) * Configuration for path normalization so that normalization can be configured for internal only use and/or forwarding. Signed-off-by: Asra Ali <asraa@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 236107df5d15381ccf5040c0cb0f163ece9627a2
4 years ago
"//envoy/type/http/v3:pkg",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
"//envoy/type/matcher/v3:pkg",
"//envoy/type/metadata/v3:pkg",
"//envoy/type/tracing/v3:pkg",
"//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",
api: freeze of v2 API, cut v4alpha API. (#10672) This patch performs a major version freeze and bump by modifying package_version_status, using the tooling developed in #10636. Specifically: v2 APIs are frozen (except for where they are the latest in their package history and still active) v3 APIs are transitioned to be active Candidate v4alpha APIs are generated (not used by Envoy yet) Fixes #10355 Risk level: medium (entire API's files are modified, visually verified to ensure things look sane, all tests pass) Testing: CI Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 549164c42cae84b59154ca4c36009e408aa10b52
5 years ago
],
)
# This tracks frozen versions of protos.
proto_library(
name = "frozen_protos",
visibility = ["//visibility:public"],
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
deps = [
api: straggler v2alpha1 -> v3alpha clone. (#8133) These were missed in #8125. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 1b3b4ae1180b67bee6395fab5c075896fb1964ec
5 years ago
"//envoy/admin/v2alpha:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/api/v2:pkg",
"//envoy/api/v2/auth:pkg",
"//envoy/api/v2/cluster:pkg",
"//envoy/api/v2/core:pkg",
"//envoy/api/v2/endpoint:pkg",
api: straggler v2alpha1 -> v3alpha clone. (#8133) These were missed in #8125. Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 1b3b4ae1180b67bee6395fab5c075896fb1964ec
5 years ago
"//envoy/api/v2/listener:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/api/v2/ratelimit:pkg",
"//envoy/api/v2/route:pkg",
"//envoy/config/accesslog/v2:pkg",
"//envoy/config/bootstrap/v2:pkg",
cluster: add aggregate cluster (#7967) Signed-off-by: Yan Xue <yxyan@google.com> Mirrored from https://github.com/envoyproxy/envoy @ aaafd6b2719b118f8a354e5b09a4c94f5c49ac69
5 years ago
"//envoy/config/cluster/aggregate/v2alpha:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//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",
api: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//envoy/config/filter/http/grpc_http1_reverse_bridge/v2alpha1:pkg",
grpc: add message count filter (#8531) Signed-off-by: Kuat Yessenov <kuat@google.com> Mirrored from https://github.com/envoyproxy/envoy @ e2cf41606c42cd18b5ac5fd2add9cf983ece9172
5 years ago
"//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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/filter/network/mongo_proxy/v2:pkg",
security: document threat model. (#8906) * Add an explicit threat model to the end user facing docs, link to this from SECURITY.md * Switch all Envoy extensions to use a new macro `envoy_cc_extension`, mandating that extensions declare a security posture. Extensions can also optionally declare `alpha` or `wip` status. * Tag all documentation sites with their well-known Envoy names. * Introduce tooling to automagically populate a list of known trusted/untrusted extensions in the threat model docs. * Generate API docs for extensions that depend on `google.protobuf.Empty`. This pattern is deprecated as per https://github.com/envoyproxy/envoy/issues/8933, but we need these for tooling support meanwhile. This work was motivated by oss-fuzz issue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18370 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 90d1094b32aa017f90cc8efcd379aeb143acabfc
5 years ago
"//envoy/config/filter/network/mysql_proxy/v1alpha1:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/filter/network/tcp_proxy/v2:pkg",
"//envoy/config/filter/network/thrift_proxy/v2alpha1:pkg",
security: document threat model. (#8906) * Add an explicit threat model to the end user facing docs, link to this from SECURITY.md * Switch all Envoy extensions to use a new macro `envoy_cc_extension`, mandating that extensions declare a security posture. Extensions can also optionally declare `alpha` or `wip` status. * Tag all documentation sites with their well-known Envoy names. * Introduce tooling to automagically populate a list of known trusted/untrusted extensions in the threat model docs. * Generate API docs for extensions that depend on `google.protobuf.Empty`. This pattern is deprecated as per https://github.com/envoyproxy/envoy/issues/8933, but we need these for tooling support meanwhile. This work was motivated by oss-fuzz issue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18370 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 90d1094b32aa017f90cc8efcd379aeb143acabfc
5 years ago
"//envoy/config/filter/network/zookeeper_proxy/v1alpha1:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/filter/thrift/rate_limit/v2alpha1: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/config/filter/udp/udp_proxy/v2alpha:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/grpc_credential/v2alpha:pkg",
api: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//envoy/config/listener/v2:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/metrics/v2:pkg",
"//envoy/config/overload/v2alpha:pkg",
"//envoy/config/ratelimit/v2:pkg",
"//envoy/config/rbac/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",
security: document threat model. (#8906) * Add an explicit threat model to the end user facing docs, link to this from SECURITY.md * Switch all Envoy extensions to use a new macro `envoy_cc_extension`, mandating that extensions declare a security posture. Extensions can also optionally declare `alpha` or `wip` status. * Tag all documentation sites with their well-known Envoy names. * Introduce tooling to automagically populate a list of known trusted/untrusted extensions in the threat model docs. * Generate API docs for extensions that depend on `google.protobuf.Empty`. This pattern is deprecated as per https://github.com/envoyproxy/envoy/issues/8933, but we need these for tooling support meanwhile. This work was motivated by oss-fuzz issue https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=18370 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 90d1094b32aa017f90cc8efcd379aeb143acabfc
5 years ago
"//envoy/config/retry/previous_priorities:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/config/trace/v2:pkg",
X-Ray Localized Sampling (2/2) (#9167) Signed-off-by: Marco Magdy <mmagdy@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 1a6b970f024e45746af3dc4977eec5239c64e3d3
5 years ago
"//envoy/config/trace/v2alpha:pkg",
api: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
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",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/data/tap/v2alpha:pkg",
"//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: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//envoy/service/load_stats/v2:pkg",
"//envoy/service/metrics/v2:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//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/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/service/tap/v2alpha:pkg",
api: minified v2 -> v3alpha upgrade via type dependency analysis. (#8529) This patch moves away from the paradigm of sed-style upgrading of every v2 package to v3alpha. Instead, an additional type analysis phase is performed prior to protoxform by a protoc plugin known as the "type whisperer". The type whisperer produces structured type dependency information for each .proto. The tools/type_whisperer/typedb_gen.py tool then knits these together to provide an API-wide type dependency graph. This is then used to determine which types need upgrading (either they have breaking changes or transitively depend on types with such changes). Only packages with upgraded types now undergo the v2 -> v3alpha transition. The API type database is checked into source/common/config/api_type_db.pb. This may seem a strange location, but in the future we will include the type database as a build artifact for the Envoy binary, as it will be used by the reflection-based version converter to find the type upgrade path for input proto. Risk level: Low (the v3alpha protos are not used yet). Testing: fix_format, manual inspection of diffs, bazel test //test/..., docs build. Part of #8082 Fixes #8490 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ ad57b58cfbb256af41a467260dce2a8013b7a7fa
5 years ago
"//envoy/service/trace/v2:pkg",
api/build: switch to only package level targets in API. (#8495) As part of #8082, we want to be able to (1) automatically generate BUILD files and (2) treat packages as atomic from a "upgrade / do not upgrade" decision perspective. This is simplified by having our BUILD targets at package granularity, since this is what the protoxform plugin operates on. This PR broadens the package-level treatment that was already introduced for Go in #8003 to Python and C++. This simplifies BUILD files significantly and opens the way to automated generation. There is some technical debt introduced, since all visibility controls have been removed. This is slated for reintroduction in https://github.com/envoyproxy/envoy/issues/8491. As a bonus (useful for BUILD file generation), also removed the inconsistency in BUILD package target naming for packages in envoy.api.* and envoy.type.*. E.g. //envoy/api/v2:v2 is now //envoy/api/v2:pkg. Risk level: Low (but this will break internal builds and require BUILD fixups to consuming projects). Testing: bazel test //test/... @envoy_api//... Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 4e858f17fe08224c9c089240908ccd0c518e01a7
5 years ago
"//envoy/type:pkg",
"//envoy/type/matcher:pkg",
tracing: enhance custom tags source (#8279) Signed-off-by: Yi Tang <ssnailtang@gmail.com> Mirrored from https://github.com/envoyproxy/envoy @ 222890cbff2f9d7dff74fca6535771c063104d68
5 years ago
"//envoy/type/metadata/v2:pkg",
"//envoy/type/tracing/v2:pkg",
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
],
)