[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: 85622be847

main

master-ci-test

Branches Tags

${ item.name }

Create tag ${ searchTerm }

Create branch ${ searchTerm }

from '85622be847'

${ noResults }

data-plane-api/envoy/extensions/transport_sockets/tls/v3

History

data-plane-api(Azure Pipelines) 85622be847 sds: additional support for symlink-based key rotation. (#13721) ... There are a few limitations in our existing support for symlink-based key rotation: We don't atomically resolve symlinks, so a single snapshot might have inconsistent symlink resolutions for different watched files. Watches are on parent directories, e.g. for /foo/bar/baz on /foo/bar, which doesn't support common key rotation schemes were /foo/new/baz is rotated via a mv -Tf /foo/new /foo/bar. The solution is to provide a structured WatchedDirectory for Secrets to opt into when monitoring DataSources. SDS will used WatchedDirectory to setup the inotify watch instead of the DataSource path. On update, it will read key/cert twice, verifying file content hash consistency. Risk level: Low (opt-in feature) Testing: Unit and integration tests added. Fixes #13663 Fixes #10979 Fixes #13370 Signed-off-by: Harvey Tuch <htuch@google.com> Mirrored from https://github.com/envoyproxy/envoy @ 122257ef6ade0009feafc3c9142d480260fe069f		4 years ago
..
BUILD	…
cert.proto	tls/api: factor transport socket out of cert.proto. (#10910)	5 years ago
common.proto	sds: additional support for symlink-based key rotation. (#13721)	4 years ago
secret.proto	…
tls.proto	…