Skip to content
This repository has been archived by the owner on Feb 5, 2024. It is now read-only.

docs: add instructions for chaincode upgrade #50

Closed
AurelienGasser opened this issue Apr 29, 2020 · 1 comment
Closed

docs: add instructions for chaincode upgrade #50

AurelienGasser opened this issue Apr 29, 2020 · 1 comment

Comments

@AurelienGasser
Copy link
Contributor

AurelienGasser commented Apr 29, 2020

There are currently no instructions on how to upgrade the chaincode version on a running installation.

@AurelienGasser AurelienGasser changed the title doc: add instructions for a chaincode upgrade docs: add instructions for chaincode upgrade Apr 29, 2020
@Kelvin-M
Copy link
Collaborator

Kelvin-M commented May 4, 2020

You can find more information here : https://hyperledger-fabric.readthedocs.io/en/release-1.4/chaincode4noah.html#upgrade
and https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/peerchaincode.html#peer-chaincode-upgrade-example

We have also a chaincode upgrade instructions in the docker-compose version :
https://github.com/SubstraFoundation/hlf-k8s/blob/master/python-scripts/utils/run_utils.py#L254
It is based on the fabric-sdk-py client : https://github.com/hyperledger/fabric-sdk-py/blob/master/hfc/fabric/client.py#L1395

Be careful, depending on the policy, the transaction must be endorsed by multiple peers, so you should use :

--peerAddresses stringArray
--tlsRootCertFiles stringArray

Usage example here for instance
https://hyperledger-fabric.readthedocs.io/en/release-1.4/commands/peerchaincode.html#peer-chaincode-upgrade

mblottiere added a commit that referenced this issue Sep 5, 2022
Crypto materials expired.
This regenerates them, with an expiration date in 5 years (Feb. 2027).
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants