chore(deps): update ci dependencies

[Aashiq-J]

Description

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.

[Aashiq-J]

/run pipeline

[Aashiq-J]

The changes are update in place.

[Aashiq-J]

/run pipeline

[ocofaigh]

@Aashiq-J Why are we ignoring this now?? The consistency check is to ensure the module is idempotent, and if it fails we need to know why, and not just ignore it

[Aashiq-J]

@ocofaigh ,This is similar to this provider bug, created a new provider issue for this. This error is causing all PR and continuous pipelines to fail for this module.

[Aashiq-J]

/run pipeline

[toddgiguere]

@Aashiq-J @ocofaigh I think we are going to have to add these ignores this way, at least until the provider fixes this idempotent issue. When looking at testwrapper, it only supports identification of updates (and ignoring those updates) at the resource level, not the attribute level.

[terraform-ibm-modules-ops]

:tada: This issue has been resolved in version 4.1.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: