Skip to content

Commit 0bd1ad8

Browse files
committed
updated with the review inputs from PM team
1 parent 10a1caa commit 0bd1ad8

File tree

1 file changed

+27
-9
lines changed

1 file changed

+27
-9
lines changed

articles/blockchain/templates/hyperledger-fabric-consortium-azure-kubernetes-service.md

Lines changed: 27 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -155,9 +155,10 @@ These commands will clone Azure HLF client application code from public GitHub r
155155
### Setup environment variables
156156

157157
> [!NOTE]
158-
> All environmental variables follow the Azure resource naming convention
159-
> **Set below environment variables for orderer organization client**
160-
> OrdererOrgName and PeerOrgName are the ABS resource names used to set up Orderer Service > or Peer Org respectively
158+
> All environmental variables follow the Azure resource naming convention.
159+
160+
161+
**Set below environment variables for orderer organization client**
161162

162163

163164
```bash
@@ -167,7 +168,7 @@ ORDERER_ORG_NAME=<ordererOrgName>
167168
ORDERER_ADMIN_IDENTITY="admin.$ORDERER_ORG_NAME"
168169
CHANNEL_NAME=<channelName>
169170
```
170-
Set the below environment variables for peer organization client
171+
**Set the below environment variables for peer organization client**
171172

172173
```bash
173174
PEER_ORG_SUBSCRIPTION=<peerOrgSubscritpion>
@@ -208,8 +209,10 @@ az storage share create --account-name $STORAGE_ACCOUNT --account-key $STORAGE
208209
Follow below steps for generating Azure file share connection string
209210

210211
```bash
212+
STORAGE_KEY=$(az storage account keys list --resource-group $STORAGE_RESOURCE_GROUP --account-name $STORAGE_ACCOUNT --query "[0].value" | tr -d '"')
211213
SAS_TOKEN=$(az storage account generate-sas --account-key $STORAGE_KEY --account-name $STORAGE_ACCOUNT --expiry `date -u -d "1 day" '+%Y-%m-%dT%H:%MZ'` --https-only --permissions lruwd --resource-types sco --services f | tr -d '"')
212-
AZURE_FILE_CONNECTION_STRING="https://$STORAGE_ACCOUNT.file.core.windows.net/$STORAGE_FILE_SHARE?$SAS_TOKEN"
214+
AZURE_FILE_CONNECTION_STRING=https://$STORAGE_ACCOUNT.file.core.windows.net/$STORAGE_FILE_SHARE?$SAS_TOKEN
215+
213216
```
214217

215218
### Import organization connection profile, admin user identity, and MSP
@@ -242,6 +245,21 @@ From orderer organization client, issue command to create a new channel. This co
242245
```bash
243246
./azhlf channel create -c $CHANNEL_NAME -u $ORDERER_ADMIN_IDENTITY -o $ORDERER_ORG_NAME
244247
```
248+
249+
From peer organization client, issue below command to set anchor peer(s) for the peer organization on the specified channel.
250+
251+
>[!NOTE]
252+
> Before executing this command, ensure that peer organization is added in the channel using Consortium management commands.
253+
254+
```bash
255+
./azhlf channel setAnchorPeers -c $CHANNEL_NAME -p <anchorPeersList> -o $PEER_ORG_NAME -u $PEER_ADMIN_IDENTITY
256+
```
257+
258+
`<anchorPeersList>` is a space separated list of peer nodes to be set as an anchor peer. For example,
259+
260+
- Set `<anchorPeersList>` as “peer1” if you want to set only peer1 node as anchor peer.
261+
- Set `<anchorPeersList>` as “peer1” “peer3” if you want to set both peer1 and peer3 node as anchor peer.
262+
245263
### Consortium management commands
246264

247265
>[!NOTE]
@@ -286,17 +304,17 @@ Similarly, to add more peer organizations in the channel, update peer environmen
286304

287305
```bash
288306
# peer organization name where chaincode operation is to be performed
289-
ORGNAME=<ABS resource name for the Peer Org>
307+
ORGNAME=<PeerOrgName>
290308
USER_IDENTITY="admin.$ORGNAME"
291-
# If you are using chaincode_example02 then set CC_NAME=chaincode_example02”
309+
# If you are using chaincode_example02 then set CC_NAME=chaincode_example02”
292310
CC_NAME=<chaincodeName>
293-
# If you are using chaincode_example02 then set CC_VERSION=1” for validation
311+
# If you are using chaincode_example02 then set CC_VERSION=1” for validation
294312
CC_VERSION=<chaincodeVersion>
295313
# Language in which chaincode is written. Supported languages are 'node', 'golang' and 'java'
296314
# Default value is 'golang'
297315
CC_LANG=<chaincodeLanguage>
298316
# CC_PATH contains the path where your chaincode is place.
299-
# If you are using chaincode_example02 to validate then CC_PATH=/home/<username>/azhlfTool/chaincode/src/chaincode_example02”
317+
# If you are using chaincode_example02 to validate then CC_PATH=/home/<username>/azhlfTool/chaincode/src/chaincode_example02/go
300318
CC_PATH=<chaincodePath>
301319
# Channel on which chaincode is to be instantiated/invoked/queried
302320
CHANNEL_NAME=<channelName>

0 commit comments

Comments
 (0)