feat: add support for deploying ocp in custom cloud endpoints

[Aashiq-J]

Description

Add support to deploy to custom cloud endpoint.

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

[Aashiq-J]

/run pipeline

[vbontempi]

I am not sure this is the right way to address it, we should make the script to verify the value of an env var and to fall back to the default value if not set

More, we mustn't expose not public endpoints on public code/documentation

[Aashiq-J]

/run pipeline

[Aashiq-J]

/run pipeline

[Aashiq-J]

/run pipeline

[vbontempi]

just a comment, the changes are ok for me now

[Aashiq-J]

/run pipeline

[vbontempi]

ok to me

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.36.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀