feat: add scc workload protection agent DA

[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]

Can you also update .catalog-onboard-pipeline.yaml so pipeline onboards it (set mark_ready: false for this flavor for now). It means you will also need some pre-validation and post validation scripts to deploy prereqs for catalog validation that will deploy WP instance and cluster. You can use the same tf code you added foe the pr tests. Here is an example of how to achieve it:

• pre-validation-deploy-slz-roks-and-obs-instances.sh
• post-validation-destroy-slz-roks-and-obs-instances.sh

[akocbek]

/run pipeline

[akocbek]

/run pipeline

[akocbek]

/run pipeline

[terraform-ibm-modules-ops]

:tada: This PR is included in version 1.10.0 :tada:

The release is available on:

• GitHub release
• v1.10.0

Your semantic-release bot :package::rocket: