feat: region dropdown in ibm_catalog

[kierramarie]

Description

Updated region variable in ibm_catalog.json to use a dropdown.

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.

[kierramarie]

/run pipeline

[whoffler]

Should Osaka jp-osa also be an option here?

[ocofaigh]

yes it should. As per the var description, the region here is: "Region where Code Engine and Container Registry resources will be provisioned." jp-osa is a supported code engine region - @kierramarie please review the regions used here against the services

[kierramarie]

Okay, I will add Osaka. Also, Montreal is supported in Code Engine and not in container registry and us-east is supported in CR and not in CE. How would you like me address those?

[kierramarie]

@ocofaigh

[ocofaigh]

To be honest Im not too worried here, as by default the DA will not create a code engine project or container registry namespace.

[ocofaigh]

Please see comments - the list of region is not accurate it seems

[kierramarie]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 2.0.5 🎉

The release is available on:

• GitHub release
• v2.0.5

Your semantic-release bot 📦🚀