fix: update default values inside override.json

[akocbek]

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.

[akocbek]

/run pipeline

[ocofaigh]

thanks @akocbek - did you try a test to ensure the override works now with one of the patterns? (you would have to set override = true to test it).

[akocbek]

we had to remove activity_tracking and metrics_monitoring because they require valid CRN (e.q. activity_tracker_crn) which we don't have it at that stage. If we remove activity_tracker_crn or metrics_monitoring_crn only then we get the following:

│ The given value is not suitable for module.roks_landing_zone.module.landing_zone.var.cos declared at ../../variables.tf:480,1-15: element 0: attribute "buckets": element 0: attribute "metrics_monitoring":
│ attribute "metrics_monitoring_crn" is required.

[akocbek]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 5.15.2 🎉

The release is available on:

• GitHub release
• v5.15.2

Your semantic-release bot 📦🚀