[FAB-10076] Peer runner fails to list instantiated cc

The peer runner integration test currently fails to get the
instantiated chaincodes. This is due to the new pluggable
validation and the "GetInstantiatedChaincodes" policy not
existing at the correct scope. This CR adds the default VSCC
plugin information to core.yaml for the peer integration runner
and properly sets the default policy for "GetInstantiatedChaincodes"
to be channel-scoped instead of peer-scoped.

Change-Id: I763b3d84ebefc3af6a3c0dc5e841ae9999312969
Signed-off-by: Will Lahti <wtlahti@us.ibm.com>

Author: wlahti

core/aclmgmt/defaultaclprovider.go

@@ -55,7 +55,6 @@ func (d *defaultACLProvider) initialize() {
 	//-------------- LSCC --------------
 	//p resources (implemented by the chaincode currently)
 	d.pResourcePolicyMap[resources.Lscc_Install] = ""
-	d.pResourcePolicyMap[resources.Lscc_GetInstantiatedChaincodes] = ""
 	d.pResourcePolicyMap[resources.Lscc_GetInstalledChaincodes] = ""
 
 	//c resources
@@ -64,6 +63,7 @@ func (d *defaultACLProvider) initialize() {
 	d.cResourcePolicyMap[resources.Lscc_ChaincodeExists] = CHANNELREADERS
 	d.cResourcePolicyMap[resources.Lscc_GetDeploymentSpec] = CHANNELREADERS
 	d.cResourcePolicyMap[resources.Lscc_GetChaincodeData] = CHANNELREADERS
+	d.cResourcePolicyMap[resources.Lscc_GetInstantiatedChaincodes] = CHANNELREADERS
 
 	//-------------- QSCC --------------
 	//p resources (none)

integration/runner/testdata/core.yaml

@@ -121,6 +121,9 @@ peer:
         endorsers:
           escc:
             name: DefaultEndorsement
+        validators:
+          vscc:
+            name: DefaultValidation
     validatorPoolSize:
 
 vm: