refactor: Split observability DA into 3 DA's

[vkuma17]

Description

Split observability DA into 3 DA's

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.

[ocofaigh]

/run pipeline

[ocofaigh]

Approved this and will merge when green, however we will need to revisit it when the VPC "Fully configurable" variation is moved to the landing zone tile

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[ocofaigh]

@Vipin654 Before you re-trigger a new pipeline run it might help if you left a comment with the failure reason of previous run. Then we can start to understand if its the same error, or different errors, and the frequency of each error

[vkuma17]

Sure @ocofaigh I will do that from next time. I have seen 2 errors since yesterday. One was where cost estimation failed for SCC WP with a 403 error but it happened only once or twice and other is that schematics job is still running for creating the cluster but status in projects changes to failed which when returned in our addon tests, fails the test. I have reported in epx-projects.

[vkuma17]

Doing a pipeline run with us-south region for the addon test. When pipelines were running with us-south as the region, i didn't see the issue of projects going into failed state even though job is still running in schematics. Most probably it is not the issue but just doing one more run for confirming.

[vkuma17]

/run pipeline

[vkuma17]

/run pipeline

[vkuma17]

last two pipelines failed with a bug in testwrapper. I found the bug and i will raise a PR for the fix tomorrow

[vkuma17]

trying once with new version of testwrapper.

[vkuma17]

/run pipeline

[vkuma17]

last pipeline run failed because of issue in other test . Addon test passed. Re-running pipeline one more time. Below is the current error.
2025-09-08T09:56:55.8705160Z �[31m│�[0m �[0mid: terraform-c907de16 2025-09-08T09:56:55.8705690Z �[31m│�[0m �[0msummary: 'DeleteSubnetWithContext on retry failed: timeout while waiting for state 2025-09-08T09:56:55.8706531Z �[31m│�[0m �[0m to become ''deleting, done, '' (last state: ''resources_attached'', timeout: 10m0s)' 2025-09-08T09:56:55.8707277Z �[31m│�[0m �[0mseverity: error 2025-09-08T09:56:55.8707628Z �[31m│�[0m �[0mresource: ibm_is_subnet

[vkuma17]

/run pipeline

[ocofaigh]

@Vipin654 If you can confirm manual tests look good (apart from undeploy which we know has an issue), I am going to propose we force merge this to unblock remaining tasks and keep working with the EPX teams on the issues we are seeing. Do you agree?

[vkuma17]

@ocofaigh i just skipped the test. i have done a thorough manual validation, we should be good. I am running the pipeline

[vkuma17]

/run pipeline

[ocofaigh]

Thanks @Vipin654 Please create a GIT issue to add it back. And maybe create a draft PR that we can re-run on demand with the tests re-enabled so we can test as EPX fixes are pushed to prod.

[vkuma17]

Created branch and issue to unskip the test @ocofaigh. I am keeping it on my board as I will be following up with projects team.
#788 - draft PR
https://github.ibm.com/GoldenEye/issues/issues/15920

[terraform-ibm-modules-ops]

🎉 This PR is included in version 3.57.0 🎉

The release is available on:

• GitHub release
• v3.57.0

Your semantic-release bot 📦🚀