Improve peer CLI error message when no orderer address passed #1555
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For peer CLI commands that require an orderer address, the peer does best effort attempt to retrieve orderer address from channel config if the orderer address is not passed (it currently only checks the deprecated Orderer.Addresses, not the org level OrdererEndpoints). The best effort attempt may be removed in a future release, so for now improve the error message to indicate that orderer address should be passed using -o flag. Signed-off-by: David Enyeart <enyeart@us.ibm.com>
caod123
approved these changes
Jul 8, 2020
|
@Mergifyio backport release-2.2 |
|
Command
|
mergify bot
pushed a commit
that referenced
this pull request
Jul 8, 2020
For peer CLI commands that require an orderer address, the peer does best effort attempt to retrieve orderer address from channel config if the orderer address is not passed (it currently only checks the deprecated Orderer.Addresses, not the org level OrdererEndpoints). The best effort attempt may be removed in a future release, so for now improve the error message to indicate that orderer address should be passed using -o flag. Signed-off-by: David Enyeart <enyeart@us.ibm.com> (cherry picked from commit 6ef8f3d)
|
Command
|
denyeart
added a commit
that referenced
this pull request
Jul 8, 2020
For peer CLI commands that require an orderer address, the peer does best effort attempt to retrieve orderer address from channel config if the orderer address is not passed (it currently only checks the deprecated Orderer.Addresses, not the org level OrdererEndpoints). The best effort attempt may be removed in a future release, so for now improve the error message to indicate that orderer address should be passed using -o flag. Signed-off-by: David Enyeart <enyeart@us.ibm.com> (cherry picked from commit 6ef8f3d)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
For peer CLI commands that require an orderer address, the peer
command does best effort attempt to retrieve orderer address from channel
config if the orderer address is not passed (it currently only
checks the deprecated Orderer.Addresses, not the org level
OrdererEndpoints). The best effort attempt may be removed in
a future release, so for now improve the error message
to indicate that orderer address should be passed using
-o flag.
Signed-off-by: David Enyeart enyeart@us.ibm.com