Skip to content

Commit f8a7127

Browse files
author
NIKHIL E GUPTA
committed
[FAB-15334] remove service discovery dislaimer
Change-Id: I65c40745ff2425c4819c2ec7c761164656d6707a Signed-off-by: NIKHIL E GUPTA <negupta@us.ibm.com>
1 parent f795c85 commit f8a7127

File tree

1 file changed

+0
-12
lines changed

1 file changed

+0
-12
lines changed

docs/source/discovery-overview.rst

Lines changed: 0 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,18 +1,6 @@
11
Service Discovery
22
=================
33

4-
.. note:: The new Fabric chaincode lifecycle has limitations in the v2.0 alpha
5-
release: in particular, it does not support using service discovery to
6-
discover a chaincode endorsement policy. Chaincodes that are installed
7-
and instantiated with the `previous lifecycle process <https://hyperledger-fabric.readthedocs.io/en/release-1.4/chaincode4noah.html>`
8-
are still discoverable with the Fabric v2.0 Alpha if the channel
9-
capabilities are set with V1_4 as the highest version enabled in the
10-
Application Capabilities section of the `configtx.yaml file <https://github.com/hyperledger/fabric/blob/release-2.0/sampleconfig/configtx.yaml>`_.
11-
The chaincode defined after enabling V2_0 capability on a channel
12-
will not be discoverable via service discovery while the existing
13-
chaincode will continue to work as before.
14-
15-
164
Why do we need service discovery?
175
---------------------------------
186

0 commit comments

Comments
 (0)