Chiebot-Mirror
/
data-plane-api
8
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

It's macOS. (#5498)

Browse Source 
Signed-off-by: Piotr Sikora <piotrsikora@google.com>

Mirrored from https://github.com/envoyproxy/envoy @ 701d422375a218c95281894df968c955831f219f
pull/620/head
data-plane-api(CircleCI) 6 years ago
parent 5ecf01e4e4
commit 8441c74aff
1 changed files with 1 additions and 1 deletions
Whitespace
Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL
Unified View
Diff Options
Show Stats Download Patch File Download Diff File
  1. 2
      XDS_PROTOCOL.md

2
XDS_PROTOCOL.md
Unescape View File

@ -16,7 +16,7 @@ proto payload in all methods. We discuss each type of subscription below.
The simplest approach to delivering dynamic configuration is to place it at a The simplest approach to delivering dynamic configuration is to place it at a
well known path specified in the well known path specified in the
[`ConfigSource`](https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/config_source.proto#core-configsource). [`ConfigSource`](https://www.envoyproxy.io/docs/envoy/latest/api-v2/api/v2/core/config_source.proto#core-configsource).
Envoy will use `inotify` (`kqueue` on Mac OS X) to monitor the file for changes Envoy will use `inotify` (`kqueue` on macOS) to monitor the file for changes
and parse the `DiscoveryResponse` proto in the file on update. Binary and parse the `DiscoveryResponse` proto in the file on update. Binary
protobufs, JSON, YAML and proto text are supported formats for the protobufs, JSON, YAML and proto text are supported formats for the
`DiscoveryResponse`. `DiscoveryResponse`.

Write Preview
Loading…
Cancel
Save