Skip to content
Permalink

Comparing changes

This is a direct comparison between two commits made in this repository or its related repositories. View the default comparison for this range or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: Tubitv/envoy-node
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d6f5118b8e8187573d5d48180c6073e9b7dbd7dc
Choose a base ref
..
head repository: Tubitv/envoy-node
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: e4b67d5967c89bb38349e67557ce38edba3a4b45
Choose a head ref
10 changes: 5 additions & 5 deletions README.md
Original file line number Diff line number Diff line change
@@ -11,7 +11,7 @@ static_resources:
listeners:
- name: egress_listener
address:
socket_address:
socket_address:
address: 0.0.0.0
port_value: 12345
filter_chains:
@@ -113,7 +113,7 @@ For gRPC, you can new the client like this:
#### General RPC

```js
const grpc = require("grpc");
const grpc = require("@grpc/grpc-js");
const { envoyProtoDecorator, GrpcRetryOn } = require("envoy-node");

const PROTO_PATH = __dirname + "/ping.proto";
@@ -303,16 +303,16 @@ new EnvoyContext({
* migrated. Fill this set for the migrated service.
* This field is default to `undefined` which means all traffic will be route to envoy.
* If this field is set to `undefined`, this library will also try to read it from `x-tubi-envoy-managed-host`.
* You can set in envoy config, like this:
*
* You can set in envoy config, like this:
*
* ``yaml
* request_headers_to_add:
* - key: x-tubi-envoy-managed-host
* value: hostname:12345
* - key: x-tubi-envoy-managed-host
* value: foo.bar:8080
* ``
*
*
* If you set this to be an empty set, then no traffic will be route to envoy.
*/
envoyManagedHosts: new Set(["some-hostname:8080"]);
Loading