Skip to content

Commit f60d3af

Browse files
author
Jason Yellick
committed
[FAB-2105] Add config schema protos
https://jira.hyperledger.org/browse/FAB-2105 Because the new configtx format is so much more flexible than the original, we need to make sure that it is locked down to keep people from going crazy with it. The restrictions can be relaxed as the use cases are made, but initially the goal is to restrict the configuration to a minimal set and loosen from there. To do this, protos for a simple schema should be defined so that the configtx manager can enforce the restrictive configuration scheme. Change-Id: Iff0df7910aa216a03267beeb86b5b9f3f29d4b70 Signed-off-by: Jason Yellick <[email protected]>
1 parent 417eccb commit f60d3af

File tree

3 files changed

+120
-50
lines changed

3 files changed

+120
-50
lines changed

protos/common/common.pb.go

+3
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

protos/common/configtx.pb.go

+107-50
Some generated files are not rendered by default. Learn more about customizing how changed files appear on GitHub.

protos/common/configtx.proto

+10
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,16 @@ message ConfigTemplate {
5959
repeated ConfigItem items = 1;
6060
}
6161

62+
message ConfigGroupSchema {
63+
map<string, ConfigGroupSchema> groups = 1;
64+
map<string, ConfigValueSchema> values = 2;
65+
map<string, ConfigPolicySchema> policies = 3;
66+
}
67+
68+
message ConfigValueSchema {}
69+
70+
message ConfigPolicySchema {}
71+
6272
// This message may change slightly depending on the finalization of signature schemes for transactions
6373
message Config {
6474
ChannelHeader header = 1;

0 commit comments

Comments
 (0)