Skip to content

Releases: IBM-Blockchain/ansible-collection

v2.0.0-beta

03 Feb 10:41
e1f5d01
Compare
Choose a tag to compare
v2.0.0-beta Pre-release
Pre-release

This release is noteable as it includes support for the Fabric Open Source Stack (Fabric Operator/Fabric Operations Console)
Note Docker images will only be pushed to ghcr.io

What's Changed

New Contributors

Full Changelog: v1.2.0...v2.0.0-beta

v1.2.0 Ansible Collection

19 May 10:41
e6be80e
Compare
Choose a tag to compare

This brings in the very latest Hyperleder Fabric release, 2.4. This lets you
use the gateway functionality. Makes application connectivity much simpler

What's Changed

  • Update to support installing IBP v2.5.3 by @mbwhite in #598

Full Changelog: v1.1.6...v1.2.0

v1.1.6 Ansible Collection

18 Mar 08:49
44596c4
Compare
Choose a tag to compare

This is a maintenance release of the collection.

What's Changed

  • Support Legacy Chaincode init function in #592
  • Update the commands that call the peer binary to not capture stderr as stdout in #593
  • Update to the most recent versions of IBP and the support offering in #594
  • Update to match the IBP official YAML files in #595

Full Changelog: v1.1.5...v1.1.6

v1.1.5 Ansible Collection

01 Feb 14:07
b9c76b4
Compare
Choose a tag to compare

This is a bug-fix release for a specific issue relating to TLS certificates on Orderers.

For the chaincode tasks (approve, commit and instantiate) the underlying 'peer' command needs to contact the ordering service. Over TLS this needs to be provided with a certificate to give to the networking TLS layer; today this is done by obtaining TLS certificates for each ordering node from the channel. However these are individual certificates per node.

When the TLS certs are updated however this stops working. It is also the wrong thing to do in general for TLS - a 'root trust' certificate should be provided that can verify the certificate from the orderer.

To provide this ability a property 'orderer_name' has been added to the chaincode tasks. This should be set with the name of the ordering service - this will be queried for it's root tls certificate. And that will then be used.

For backward compatibility, checking the channel for certificates is still present, but should be considered deprecated. It is better to use the orderer_name and therefore use the correct certificate authority certificate.

v1.1.4 Ansible Collection

20 Jan 09:30
5d6c32a
Compare
Choose a tag to compare

This is a bug-fix release

  • A fix for issue #586 - the template names were incorrect when working with OCP clusters
  • When using the force-reenroll option with identities, the re-enrollment would fail with a permission denied style error. Rather than renerolling the code was attempting to enroll for the first time (again).

v1.1.3 Ansible Collection

09 Dec 14:26
9517a08
Compare
Choose a tag to compare

This is a bug fix release. Whilst the modules could take the api_timeout property, it wasn't honoured on the roles. This has been fixed.

v1.1.2 Support Kubernetes 1.22

17 Nov 11:04
15acc74
Compare
Choose a tag to compare

A number of the K8S templates were using deprecated features that have been removed in the latest 1.22 version.
These have been updated in this release. This affects the installation of the IBP and HLF Console - not the Fabric component management.

v1.1.1

27 Sep 09:25
26f208c
Compare
Choose a tag to compare

This patch releases adds in Kubernetes support as well as OpenShift for the IBM Hyperledger Fabric Support.

Also fixes have been made to the pipeline to attempt to properly publish.

v1.1.0

21 Sep 10:39
e3d13a6
Compare
Choose a tag to compare

With the launch of the IBM Support Offering for Hyperledger Fabric, this release of the ansible-collection supports this.

Two new roles have been added:

  • hlfsupport_console
  • hlfsupport_crds

Functionally these are copied from the console and crds roles, but these are targeted towards the Support Offering.
This will install the appropriate docker images on OpenShift

Tutorials and documentation have been added for these new roles as well.

For information on the Support Offering https://www.ibm.com/cloud/blockchain-platform/hyperledger-fabric-support

v1.0.7

30 Mar 09:17
ac85e27
Compare
Choose a tag to compare

This release includes:

  • Updates to the enrolled_identity module that allow you to forcibly re-enroll an identity, or automatically re-enroll an identity before it expires (#39).
  • A new channel_acl module that allows you to manage the ACLs on a channel (#551).
  • Updates to the channel_config module that allow you to specify the ACLs on a channel at channel creation time (#552).
  • A new contributing guide for the collection (#553).
  • A new tutorial and example around creating an intermediate CA (#510).
  • The operation parameter has been removed from the peer_channel and channel_block modules as it only had one possible value. No playbook changes are required, the parameter will still be accepted but ignored (#269, #272).
  • A new logging feature that allows you to gather diagnostic logs from the collection (#556).
  • A new support topic in the documentation which talks about support options and how to collect data for IBM support.