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

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

Tag: Branch: Tree: 516ea79d04

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '516ea79d04'

${ noResults }

data-plane-api/envoy/annotations

History

data-plane-api(CircleCI) 046ebe5f95 tooling: restoring runtime fatal-by-defaults and changing to fully qualified (#9591) ... Changing from relative name to absolute name, and fixing the fatal-by-defaults that were broken by the v3 switch. The old way to allow fatal-by-defaults was envoy.deprecated_features:proto_file.proto:field_name the new way is envoy.deprecated_features:full.namespace.field_name When we switched to v3, all the hard-coded v2 names stopped working. This reinstates them via hopefully more permanent proto annotation. The only remaining ugly bit is that unfortunately the full namespace and field name are the v3 versions even if the original config was v2. Between @htuch and I we should fix that before merging. Risk Level: Medium Testing: added new unit tests Docs Changes: updated Release Notes: n/a Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 156d7c90083c196a206c07fc03b2de6be8260bd3		5 years ago
..
BUILD	api/config: use resource type annotations to provide type-to-endpoint. (#9566)	5 years ago
deprecation.proto	tooling: restoring runtime fatal-by-defaults and changing to fully qualified (#9591)	5 years ago
resource.proto	api/config: use resource type annotations to provide type-to-endpoint. (#9566)	5 years ago