Sync duplicated modules

[shemau]

Description

Make sure standard (latest) versions of submodules are used.

Release required?

• [ ] No release
• [x] Patch release (x.x.X)
• [ ] Minor release (x.X.x)
• [ ] Major release (X.x.x)

Release notes content

Run the pipeline

If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.

Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:

/run pipeline

Checklist for reviewers

• [ ] If relevant, a test for the change is included or updated with this PR.
• [ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

• Use a conventional commit message to set the release level. Follow the guidelines.
• Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
• Use the Squash and merge option.

[shemau]

/run pipeline

[shemau]

/run pipelines

[shemau]

/run pipeline

[shemau]

/run pipeline

[shemau]

Some problem determination shows that the modules were getting out of sync whilst the new tests and DA solution were implemented on top of a rapidly upgrading base. This change makes sure that each module is at a consistent level and bumps the DA solution to the latest versions.

A release is requested due to a change to the CBR module in the main module.

[shemau]

/run pipeline

[shemau]

/run pipeline

[shemau]

/run pipeline

[shemau]

/run pipeline

[shemau]

/run pipeline

[shemau]

/run pipeline

[terraform-ibm-modules-ops]

:tada: This PR is included in version 1.13.2 :tada:

The release is available on:

• GitHub release
• v1.13.2

Your semantic-release bot :package::rocket: