feat: add variable to skip resetting api key

[Aashiq-J]

Description

issue: #827

Release required?

• No release
• 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]

/run pipeline

[Aashiq-J]

/run pipeline

[ocofaigh]

Left some comments. I'm not sure about hiding it from the fully configurable DA. Otherwise how is the consumer supposed to use it?

[ocofaigh]

I don't think we should call this a reset. In our module its always going to create one. So we should name this skip_cluster_apikey_creation

[ocofaigh]

Set to true to skip explicit creation of the containers-kubernetes-key for the given region and resource group. You can set this to false if you plan to manually create this key, or if you want to allow the cluster creation process to create it. Please be aware that it may take multiple apply attempts when allowing the cluster creation process to create it it before it will be successful.

[Aashiq-J]

/run pipeline

[Aashiq-J]

/run pipeline

[Aashiq-J]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.67.0 🎉

The release is available on:

• GitHub release
• v3.67.0

Your semantic-release bot 📦🚀