feat(pd): support real addrs in testnet generate #2916
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removed the default RFC1918 addresses from the
pd testnet generate
logic. Added two new options:The goal is to allow a node operator to pass in public IPv4 address information at the time of config generation, so the emitted config files are valid without further munging, particularly with respect to the
external_address
Tendermint advertises for its P2P service.This change unblocks a leaner deployment pipeline, where we actually use the results of the
pd testnet generate
output, as intended.Also: fix(pd) support urls in testnet join
We were inadvertently dropping paths on URLs by prepending
/
toUrl.join
args, which caused the join operation to be performed on the base domain, ignoring any path. We didn't notice this because all our services had been on their own subdomains.