v2.0.0 release

[ocofaigh]

Description

Update all members to the latest version versions. This update will remove logdna, so marking as a breaking change (v2.0.0)

Stack	Change
1a - Key management	v4.15.13 --> v4.16.7
1b - Object storage	v8.11.14 --> v8.14.0
2 - Observability	v1.19.0 --> v2.1.0
3 - Event Notifications	v1.10.19 --> v1.14.0
4a - Security and Compliance Center	v1.20.2 --> v1.21.0
4b - Secrets Manager	v1.18.6 --> v1.18.12

Release required?

• No release
• Patch release (x.x.X)
• Minor release (x.X.x)
• Major release (X.x.x)

Release notes content

• 1a - Key management - v4.15.13 --> v4.16.7
  • dependency updates
• 1b - Object storage - v8.11.14 --> v8.14.0
  • dependency updates
  • updated the KMS auth policy so its scoped to the exact KMS Key. NOTE: This will delete and re-create any existing auth policy, however it will create before delete so there will be no disruption to every day services.
• 2 - Observability - v1.19.0 --> v2.1.0
  • dependency updates
  • removed Log Analysis support - this will delete the Log Analysis instance and resource key on upgrade.
  • updated the KMS auth policy so its scoped to the exact KMS Key. NOTE: This will delete and re-create any existing auth policy, however it will create before delete so there will be no disruption to every day services.
  • Enabled Event Notifications integration for Cloud Logs
• 3 - Event Notifications - v1.10.19 --> v1.14.0
  • updated the KMS auth policy so its scoped to the exact KMS Key. NOTE: This will delete and re-create any existing auth policy, however it will create before delete so there will be no disruption to every day services.
  • updated the configuration in the DA that is used to stored failed events in a COS bucket to now use the direct COS endpoint by default (previously it was using the public endpoint). This change is done as an update in place.
  • Updated the configuration of the COS bucket so the Monitoring instance is no longer explicitly passed to it. The bucket metrics will still be monitored, however metrics will be sent to the instance associated to the container's location unless otherwise specified in the Metrics Router service configuration. This change is done as an update in place.
  • An update in place will be done on the KMS key rings since the force_delete option has been deprecated by the service. This has no impact to any services as the value is not being used by the backend.
• 4a - Security and Compliance Center - v1.20.2 --> v1.21.0
  • updated the KMS auth policy so its scoped to the exact KMS Key. NOTE: This will delete and re-create any existing auth policy, however it will create before delete so there will be no disruption to every day services.
• 4b - Secrets Manager - v1.18.6 --> v1.18.12
  • An update in place will be done on the KMS key ring since the force_delete option has been deprecated by the service. This has no impact to any services as the value is not being used by the backend.

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.

[ocofaigh]

/run pipeline

[ocofaigh]

/run pipeline

[ocofaigh]

/run pipeline

[ocofaigh]

/run pipeline

[ocofaigh]

/run pipeline

[terraform-ibm-modules-ops]

🎉 This PR is included in version 2.0.0 🎉

The release is available on:

• GitHub release
• v2.0.0

Your semantic-release bot 📦🚀