0.0.8

Merge pull request #123 from sstone1/issue-120

Delete components in software when state set to absent (resolves #120)

0.0.7

This release includes the publishing of a Docker image, ibmblockchain/vscode-prereqs, that will be used by the IBM Blockchain Platform extension for Visual Studio Code for standing up local Hyperledger Fabric networks.

0.0.6

This release contains the fix for #114, where the wrong volume name was being used to create the data volume for all peers. This meant that the data volumes did not have any labels applied from playbook variables, making them more difficult to find with automated scripts.

0.0.5

This release contains an updated fix for #111. The previous fix was not correct; network aliases are needed as well as the hostnames, and the common name in TLS certificates was set to the name rather than the hostname.

0.0.4

This release contains the fix for issue #111, where hostnames for Docker containers are not set, leading to networking errors between peer and ordering nodes. This fix requires that you update your playbooks to add a new hostname property to the docker section for each CA, peer, and orderer.

0.0.3

Various minor updates - removing the dependency on Hyperledger's Nexus server in #101, updating the Alpine Linux and Docker versions used to build the Docker image in #103, and ignoring test generated files in #107. There's also a fix in #105 that corrects the mod_policy for the Readers and Writers policies on a channel from Readers and Writers respectively to Admins in line with the Fabric v1.4/v2.0 defaults.

0.0.2

This release contains the fix for issue #97, where this role fails to delete the peer data volume when state is set to absent. This bug can lead to behaviour where the peer is restarted with the old peer data volume, which contains stale and invalid channel and configuration information.

0.0.1

Initial release of the Ansible role for managing Hyperledger Fabric v1.4 networks using the IBM Blockchain Platform. This version is functional, and can be used for development/test purposes. However, please be aware that the configuration and example playbooks are likely to change in future releases.