feat: Add the ability to define the scope of SCC attachement

[jor2]

Description

Add the ability to define the scope of SCC attachement

Release required?

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

Release notes content

Add the ability to define the scope of SCC attachement

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]

see comments

[ocofaigh]

@jor2 you may also want to consider including this change too #149

[jor2]

/run pipeline

[jor2]

/run pipeline

[ocofaigh]

@jor2 can you check my comment?

[ocofaigh]

Oh @jor2 The new inputs need to be added to ibm_catalog.json - you should make the attachment_schedule a dropdown with the supported values

[SirSpidey]

Suggestions for some descriptions. Let me know if they don't make sense.

[jor2]

Oh @jor2 The new inputs need to be added to ibm_catalog.json - you should make the attachment_schedule a dropdown with the supported values

updated, is that what you meant by dropdown?

[ocofaigh]

the order of the variables here matter, as thats the order they show in the UI. We try to group related variables together. You after adding this between kms_endpoint_type and scc_cos_key_ring_name which are both KMS related vars. Can you group the attachment related variables together. You also need to add resource_groups_scope too so it gets ordered

[jor2]

/run pipeline

[jor2]

/run pipeline

[SirSpidey]

I'll approve, but I think this might need attention:

ibm_cloud.json

• support_details: Should probably use the one we put in security-services:

If you’re experiencing issues with this product, review the troubleshooting information available from the “Docs” link in the Related links section. If you can’t resolve your problem, click “Get help” in the related links and create a case.

[ocofaigh]

@SirSpidey The support_details were added to all of the DAs in the community registry. There is no cloud docs to link to for those DAs. And they are not supported through support cases as they are not in main catalog

[terraform-ibm-modules-ops]

🎉 This issue has been resolved in version 1.15.0 🎉

The release is available on:

• GitHub release
• v1.15.0

Your semantic-release bot 📦🚀