The current scripts download the fabric binaries and place them
in `/usr/local`. Modifying the host system in CI is generally
bad practice. The `bootstrap.sh` script also downloads the
binaries into the root of the `fabric-samples` repo. It is
good practice for us to do the same in CI. We also have
several samples that make an assumption about the location
of these scripts. In the future we should re-evaluate these
examples.
Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
initLedger must be called instead of init, that does not exist.
That also keeps consistency between the "with TLS" and "withtout" TLS cases.
Signed-off-by: Jonathan Gross <woodyjon@gmail.com>
echo Generating channel configuration transaction 'channel.tx'
it will be output to the console "configtxgen -profile TwoOrgsChannel -outputCreateChannelTx ./channel-artifacts/channel.tx -channelID mychannel"
Signed-off-by: KIM GEONWOO <kgw8919@gmail.com>
Add sample which can be used with the builder scripts described in
the "Chaincode as an external service" documentation
Signed-off-by: James Taylor <jamest@uk.ibm.com>
Description
The use of Orderer.Addresses in configtx.yaml is deprecated, and Organizations.<Org>.OrdererEndpoints should be used instead. Therefore, update all the fabric-samples configtx.yaml files.
Related issues
https://jira.hyperledger.org/browse/FAB-17504
Signed-off-by: xu wu <wuxu1103@163.com>
The CA's are not part of the `test` docker network. So
applications written and hosted on the `test` network
cannot interact with the CA
Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
This reverts commit 9ef61e2d72.
Introduced regressions when running without explicitly specifying
a chaincode label
Signed-off-by: Brett Logan <brett.t.logan@ibm.com>
Have the application read the common connection profile to
build a JSON object used for the gateway connect and for
a fabric-ca client instance.
Signed-off-by: Bret Harrison <beharrison@nc.rr.com>
Change 2.0.0-beta to 2.0.0 when CommercialPaper uses the test network
Add test network to the azure pipelines
Correct test network envvar script
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
* WIP Commercial Paper -> Test network
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
* Update Commercial Paper to v2.0 lifecycle
- move to using the test-network
- updating README.md to include commands to use v2.0 lifecylce
- update Contracts and Applications to use 2.0 libraries
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
This patch fixes some wrong artifact names for fabric-ca in
`fabric-samples/test-network/network.sh`.
Artifacts names which include `issuerPublicKey` and `issuerRevocationPublicKey`
should start with capital letters.
Due to the wrong names, some files remain even after running the command to
bring down networks using fabric-ca.
Signed-off-by: Tatsuya Sato <Tatsuya.Sato@hal.hitachi.com>
Update the applications and scripts to use the new v2
SDKs and the new lifecycle
Add in a basic script based on the readme.md that does
a basic run of the scenario
Signed-off-by: Matthew B White <whitemat@uk.ibm.com>
