Split observability da #366
Conversation
|
TODO: Need to bump Event Notification version once EN PR is merged. |
|
/run pipeline |
…ules/terraform-ibm-secrets-manager into split-observability-da
|
/run pipeline |
|
/run pipeline |
|
/run pipeline |
There was a problem hiding this comment.
Activity tracker and Cloud Logs is missing from dependencies. I also think we should wait for new EN version after terraform-ibm-modules/terraform-ibm-event-notifications#489 is merged - Im pushing to get that PR in asap
…ules/terraform-ibm-secrets-manager into split-observability-da
|
EN dependency PR is merged terraform-ibm-modules/terraform-ibm-event-notifications#524, I have updated code to consume latest EN and test wrapper version. |
|
/run pipeline |
| { | ||
| "name": "deploy-arch-ibm-observability", | ||
| "description": "Enables provisioning and configuration of IBM Cloud Logs to collect, route, analyze, and visualize platform logs and events — including those generated by the Event Notifications instance — for enhanced visibility, alerting, and troubleshooting.", | ||
| "name": "deploy-arch-ibm-cloud-logs", |
There was a problem hiding this comment.
Just started looking at doing this for Event Streams does Cloud Logs have a dependency on COS?
There was a problem hiding this comment.
I think yes, Cloud Logs have dependency on COS
There was a problem hiding this comment.
Ah, so COS is automatically added as an addon because it is a dependency of an enabled addon
When COS is disabled the user would have to supply the existing_cos_instance_crn themselves... got it, thanks
|
@rajatagarwal-ibm when are you planning to complete this one? OCP DA is dependent on SM DA. |
|
@maheshwarishikha thanks for checking in. As far as I remember someone from India team was working on some dependency of SM last week. I didn't get a chance to look if that's completed or not. |
|
@rajatagarwal-ibm The dependency was fixed in terraform-ibm-modules/terraform-ibm-activity-tracker#77 2 weeks ago. Please use Activity Tracker version v1.2.12 |
|
/run pipeline |
|
@ocofaigh yes as per our discussion in the scrum, all the changes were already in. Re-ran the pipeline |
|
🎉 This PR is included in version 2.8.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Description
Release required?
x.x.X)x.X.x)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:
Checklist for reviewers
For mergers