feat: add support for paramters for ocp addons

[Aashiq-J]

Description

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

[Aashiq-J]

/run pipeline

[ocofaigh]

@toddgiguere Im ok with this approach - any concerns?

[toddgiguere]

This looks good to me, in fact I think it is a very good improvement over the old method. In the old method if the "version" was null then that meant you didn't want to install, and also meant you had to supply a version for ones you do want.

I just verified, according to documentation:

version- (Optional, String) The add-on version. Omit the version that you want to use as the default version.This is required when you want to update the add-on to specified version.

So with this new solution, someone could make the "object" not null, but keep "version" null, which will use default version. A bit more flexible I think.

I do wish we could get rid of the csi driver though.

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.49.0 🎉

The release is available on:

• GitHub release
• v3.49.0

Your semantic-release bot 📦🚀