problem: using "upstreams" on two levels of config is confusing

This commit is contained in:
Igor Artamonov
2020-03-23 23:41:32 -04:00
parent 014461520e
commit 695b38f702
6 changed files with 6 additions and 6 deletions

View File

@@ -76,7 +76,7 @@ proxy:
- id: kovan - id: kovan
blockchain: kovan blockchain: kovan
upstreams: cluster:
upstreams: upstreams:
- id: infura-eth - id: infura-eth
chain: ethereum chain: ethereum

View File

@@ -3,7 +3,7 @@ port: 2449
tls: tls:
enabled: false enabled: false
upstreams: cluster:
upstreams: upstreams:
- id: infura-eth - id: infura-eth
chain: ethereum chain: ethereum

View File

@@ -29,7 +29,7 @@ proxy:
blockchain: ethereum blockchain: ethereum
- id: kovan - id: kovan
blockchain: kovan blockchain: kovan
upstreams: cluster:
upstreams: upstreams:
- id: infura-eth - id: infura-eth
chain: ethereum chain: ethereum

View File

@@ -16,7 +16,7 @@ tls:
client: client:
require: true require: true
ca: "ca.crt" ca: "ca.crt"
upstreams: cluster:
include: "upstreams.yaml" include: "upstreams.yaml"
---- ----

View File

@@ -38,7 +38,7 @@ class UpstreamsConfigReader(
} }
override fun read(input: MappingNode?): UpstreamsConfig? { override fun read(input: MappingNode?): UpstreamsConfig? {
return getMapping(input, "upstreams")?.let { return getMapping(input, "cluster")?.let {
readInternal(it) readInternal(it)
} }
} }

View File

@@ -34,7 +34,7 @@ proxy:
- id: kovan - id: kovan
blockchain: kovan blockchain: kovan
upstreams: cluster:
defaults: defaults:
- chains: - chains:
- ethereum - ethereum