Node configuration not containing property "rpcSettings.address" fails with error "No configuration setting found for key 'address'"

Description

The problem with the above is that an operator will immediately try and put a top-level "address" property, rather than adding that inside the "rpcSettings" block, resulting in: "Unknown configuration keys: [address]." (which is correct in general, but maddening in this case).

From a brief look, it looks like recent changes to RpcSettings turning "address" and "adminAddress" from optional to mandatory triggered the error.

The solution should add the path of the property to the error message.

Activity

Show:
Ben Abineri
May 24, 2018, 8:45 AM

java.lang.IllegalArgumentException: Can't provide top-level rpcAddress and rpcSettings.address (they control the same property)

Assignee

Michele Sollecito

Reporter

Ben Abineri

Labels

Sprint

None

Epic Link

None

Priority

Medium

Severity

Medium

CVSS Score

None

CVSS Vector

None

Due Date

None

Engineering Teams

None

Fix versions

None

Affects versions

None

Ported to...

None

Story Points / Dev Days

3
Configure