v0.0.54

This release includes:

• The endorsing_organization and ordering_organization roles now allow you to specify the desired wallet directory and/or the desired file paths for the certificate authority and organization administrator identity files (#488).

v0.0.53

This release includes:

• A fix for #485, where organizations in Hyperledger Fabric v2.x networks did not have an Endorsement policy.
• Various reliability updates for slow/dodgy network connections as found during automated testing.

v0.0.52

This release includes:

• The IBM Blockchain Platform 2.5.1 fix pack 1 2.5.1-20201119 is installed by default (#483).
• Automated testing has now been extended to cover SaaS and software, Docker and non-Docker, and the tutorials (#482).

v0.0.51

This release includes:

• An update to the Docker image to include Hyperledger Fabric v2.2.1 binaries, suitable for use with the new chaincode lifecycle.
• Updates to the documentation to recommend that you pass -u $(id -u) to docker run to avoid permission problems on Linux.

v0.0.50

This release includes:

• A fix for the missing semantic_version Python module from the published Docker image (#478) from @btl5037.
• Removal of the old docker/Dockerfile to avoid the above happening again (#479).
• Switching the tutorial from using Fabric v1.x lifecycle to Fabric v2.x lifecycle now that IBP 2.5.1 has been released for SaaS/software (#480).

v0.0.49

This release includes:

• The default version of the IBM Blockchain Platform that is installed is now IBM Blockchain Platform 2.5.1 (#473). See the "What's new" section of the documentation here for details: https://cloud.ibm.com/docs/blockchain-sw-251?topic=blockchain-sw-251-whats-new
• New task guides from @rthatcher (thanks Rob!) for enabling Fabric v2.x capabilities on existing networks, creating a highly available certificate authority, and updating channel parameters such as block timeout and block size (#462).
• Version range specification support for the certificate_authority, peer, ordering_service, and ordering_service_node modules (#475). This allows you to specify a version range such as version: ">=2.2,<3.0" for a component, and the best matching version will be picked. This will also allow for automatic upgrades to new versions, but within a range that you define.
• A bug fix for the crds role so that if you specify a Kubernetes namespace or Red Hat OpenShift project other than ibpinfra, then the conversion webhook works properly (#471).

Please note that this release now has a dependency on the semantic_version Python module for handling version range specifications (#475). The Docker image now includes this Python module. If you have installed Ansible yourself, then you will not be able to use the new version range specification feature until you install this Python module. You can install this Python module using pip install semantic_version.

v0.0.48

This release includes:

• An update to the certificate_authority, peer, ordering_service, and ordering_service_node modules to use the default storage class configured for the IBM Blockchain Platform instance (#468). Before this change, the default storage class was used, and you had to override it for all components when the default storage class was not available.

v0.0.47

This release includes:

• The default version of the IBM Blockchain Platform that is installed is now IBM Blockchain Platform 2.5.0 with the October 2020 fix pack (#464).
• Preliminary support for the upcoming IBM Blockchain Platform 2.5.1 release (#466). The main change in this release is the new API level of v1beta1.

v0.0.46

This release includes:

• Support for the HSM updates in IBM Blockchain Platform 2.5.1 (#460). The PKCS#11 proxy endpoint is now optional when using an HSM. If you specify a PKCS#11 proxy endpoint, then it will continue to work as before. If you do not specify a PKCS#11 proxy endpoint, but do specify a PKCS#11 label and pin, then the PKCS#11 library configured for your IBM Blockchain Platform instance is used.

v0.0.45

This release includes:

• An update to the console role to handle the case of the CRDs not existing (#452). You can get into this state if you delete the CRDs before you delete the console, and we did not cope with that correctly.
• An update to the console and crds roles to ensure that parameters are not only defined, but also not empty (#436). This will cause errors to be thrown if you accidentally pass the empty string into one or more parameters.
• Updates to the endorsing_organization and ordering_organization roles to validate that required parameters are defined and not empty (#455).