-
Notifications
You must be signed in to change notification settings - Fork 8.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FAB-17591] Support adding an orderer endpoint to existing config #857
Conversation
eeb29d0
to
a8ee77b
Compare
pkg/config/orderer.go
Outdated
|
||
existingOrdererEndpoints = append(existingOrdererEndpoints, endpoint) | ||
|
||
// Add anchor peers config value back to application org |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Add orderer endpoints config value back to orderer org
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I will fix it.
@hellosmallstone can you also update the example_test update config scenario to reflect adding an orderer endpoint? Thanks! |
OK, I will update it. |
Description Modify an existing channel configuration to add an orderer endpoint to an orderer org's config group. Related issues https://jira.hyperledger.org/browse/FAB-17591 Signed-off-by: xu wu <wuxu1103@163.com>
@caod123 Hi, I have updated the example_test. Please review it, thx. |
LGTM +1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@@ -284,3 +284,40 @@ func addOrdererPolicies(cg *cb.ConfigGroup, policyMap map[string]Policy, modPoli | |||
|
|||
return addPolicies(cg, policyMap, modPolicy) | |||
} | |||
|
|||
// AddOrdererEndpoints adds an orderer's endpoint to an existing channel config transaction. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AddOrdererEndpoint
vs AddOrdererEndpoints
- the Doc name doesn't match the function name.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry about it.
I fixed the two nits in #891.
if ordererAddrConfigValue, ok := ordererOrgGroup.Values[EndpointsKey]; ok { | ||
err := proto.Unmarshal(ordererAddrConfigValue.Value, ordererAddrProto) | ||
if err != nil { | ||
return fmt.Errorf("failed unmarshalling orderer org %s's endpoints: %v", orgName, err) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
two spaces in the message instead of one and we can omit the possessive.
Description Fix nits in function AddOrdererEndpoint which were imported by hyperledger#857. Signed-off-by: xu wu <wuxu1103@163.com>
Description Fix nits in function AddOrdererEndpoint which were imported by #857. Signed-off-by: xu wu <wuxu1103@163.com>
Description
Modify an existing channel configuration to add an orderer endpoint to an orderer org's config group.
Related issues
https://jira.hyperledger.org/browse/FAB-17591
Signed-off-by: xu wu wuxu1103@163.com
Type of change
Description
Additional details
Related issues