From f6bb64bea60d6d3498e2be0f053e474ad9731df1 Mon Sep 17 00:00:00 2001 From: David Enyeart Date: Wed, 27 Dec 2017 11:27:13 -0500 Subject: [PATCH] [FAB-7563] Add pvt data capability to configtx.yaml FAB-6859 introduced V1_1_PVTDATA_EXPERIMENTAL capability. This work item adds it to the sample configtx.yaml so that users know how to configure it. Change-Id: I14e1fc49caa9193543340cbd885c7988db260ac8 Signed-off-by: David Enyeart --- sampleconfig/configtx.yaml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/sampleconfig/configtx.yaml b/sampleconfig/configtx.yaml index bed1d8833e2..779e7308b13 100644 --- a/sampleconfig/configtx.yaml +++ b/sampleconfig/configtx.yaml @@ -169,7 +169,6 @@ Profiles: Organizations: - *SampleOrg - # SampleNoConsortium is very similar to SampleInsecureSolo, except it does # not define Consortiums. SampleNoConsortium: @@ -357,6 +356,12 @@ Capabilities: # modification of which would cause imcompatibilities. Users should # leave this flag set to true. V1_1: true + # V1_1_PVTDATA_EXPERIMENTAL is an Application capability to enable the + # private data capability. It is only supported when using peers built + # with experimental build tag. When set to true, private data + # collections can be configured upon chaincode instantiation and + # utilized within chaincode Invokes. + V1_1_PVTDATA_EXPERIMENTAL: false ################################################################################ #