diff --git a/docs/source/policies/policies.md b/docs/source/policies/policies.md index f0433cd5b8b..7abafc53656 100644 --- a/docs/source/policies/policies.md +++ b/docs/source/policies/policies.md @@ -190,6 +190,7 @@ channel policies are defined. We can use the `configtx.yaml` file in the Fabric test network to see examples of both policy syntax types. We are going to examine the `configtx.yaml` file used by the [fabric-samples/test-network](https://github.com/hyperledger/fabric-samples/blob/main/test-network/configtx/configtx.yaml) sample. +### Member Organizations Section The first section of the file defines the organizations that will be members of the channel. Inside each organization definition are the default policies for that organization, `Readers`, `Writers`, `Admins`, and `Endorsement`, although you can name your policies anything you want. @@ -204,10 +205,10 @@ become the sub-policies that the `ImplicitMeta` policies point to.
- **Click here to see an example of an organization defined with signature policies** + Click here to see an example of an organization defined with signature policies -``` + ``` - &Org1 # DefaultOrg defines the organization which is used in the sampleconfig # of the fabric.git development environment @@ -235,7 +236,11 @@ become the sub-policies that the `ImplicitMeta` policies point to. Type: Signature Rule: "OR('Org1MSP.peer')" ``` +
+ + +### Application and Roles Section The next example shows the `ImplicitMeta` policy type used in the `Application` section of the `configtx.yaml`. These set of policies lie on the @@ -252,8 +257,9 @@ create.
- **Click here to see an example of ImplicitMeta policies** + Click here to see an example of ImplicitMeta policies + ``` ################################################################################ # @@ -289,6 +295,7 @@ Application: &ApplicationDefaults Type: ImplicitMeta Rule: "MAJORITY Endorsement" ``` +
## Fabric chaincode lifecycle