Releases: IBM-Blockchain/ansible-collection
Releases · IBM-Blockchain/ansible-collection
v0.0.24
This release includes:
- Changes to all modules so that all secure parameters you pass in are not logged (#270)
- Changes to the
console
role so you can specify zones for a multi-zone cluster (#249) - Document the requirement for Fabric v1.4.3 binaries and ensure that this version is used (#265)
- Update the documentation for all modules so examples are provided, and the documentation is complete
v0.0.23
This release includes:
- Changes to the tutorial to use
vars_files
in the Ansible playbooks instead of passing in the variable files using--extra-vars
on the CLI (#250). This change makes it much easier to run the Ansible playbooks, and makes it easier to see which variable files and variables are used by each playbook. - Updates to the
console
role to install the May fixpack for IBM Blockchain Platform v2.1.3 by default (#254). - Changes to handle HTTP 404 Not Found errors when you delete resources in Kubernetes, but not in the IBM Blockchain Platform console (#253). When
state: present
, if this situation occurs, the orphaned component will be deleted from the IBM Blockchain Platform console before creating a new component (no data can be lost, because the Kubernetes resources have already been deleted). - Changes to block the
external_ordering_service
module from orphaning resources in Kubernetes (#258). - Changes to report useful errors when users are missing Python modules (for example,
fabric-sdk-py
) or binaries (for example,peer
).
v0.0.22
This release includes:
- CRL (Certificate Revocation List) generation support for the
organization
module (#179). You need to provide both a certificate authority in thecertificate_authority
parameter and an identity in the newregistrar
parameter. This will generate arevocation_list
parameter so you don't need to. - The
endorsing_organization
andordering_organization
roles have been updated to enable CRL (Certificate Revocation List) generation support as above (#179). - Updates to the Deploying a smart contract tutorial so that it covers the registration of an application identity, and the creation of a connection profile (#241).
- Some minor fixes to variable names and comments in the tutorial (#246).
v0.0.21
This release includes:
- Improved installation requirements (#228)
- Changes to the
endorsing_organization
andordering_organization
roles to separate CA creation from identity registration (#235) - All names (organization names, peer names, etc) in the tutorial are now externalised via variables (#234)
- Various tutorial updates and fixes (#231, #233, #236, #232, #244)
- The
console
role can now accept a TLS secret name (#243)
v0.0.20
v0.0.19
v0.0.18
This release includes:
- Support for specifying the name of the peer created by the
endorsing_organization
role (#160) - Support for specifying the resources (CPU, memory) and storage for the certificate authorities, peers, and ordering services created by the
endorsing_organization
andordering_organization
roles (#211) - Bash is now part of the sample Docker image, allowing you to run the
tutorial.sh
script within Docker (#214) - Support for controlling the number of peers created by the
endorsing_organization
role (#161) - A fix for removing external ordering services that have been imported into a console (#219)
v0.0.17
This release includes:
- Support for specifying Kubernetes zones for certificate authorities, peers, and ordering services when you are using a multi-zone cluster (#26, #27, #28)
- Support for specifying the certificate authority name when using the endorsing and ordering organization roles (#197, #198)
- Support for splitting the certificate authority chain properly into root and intermediate certificates; if you have an intermediate certificate authority, then this should build the correct organisation and MSP definition (#171)
- Updates to the build a network tutorial to increase the default timeout to 10 minutes, and to document how to set the variables in the three variable files (#202)
- A fix to enable updates to certificate authorities, peers, and ordering services to work correctly (#204)