-
Notifications
You must be signed in to change notification settings - Fork 2
feat: scc wp cspm #225
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: scc wp cspm #225
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As discussed on slack, maybe we go with this:
- App Config DA:
- support creating AppConfig instance
- supports enabling config aggregator + the required trusted profile (disabled by default)
- Workload Protection DA
- supports creating WP instance
- defines the App Config DA as a dependant DA, and uses input mappings in the catalog json to enable the config aggregator
- supports enabling CSPM by taking in existing AppConfig CRN and creating WP trusted profile
|
blocked, waiting for terraform-ibm-modules/terraform-ibm-app-configuration#212 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Left some comments - I think we should move the WP trusted profile logic into the root module
|
/run pipeline |
|
/run pipeline |
main.tf
Outdated
| # but profile can only exist after instance has been created | ||
| # hence we cannot directly enable CSPM in the instance creation | ||
| # and need to use a separate resource to enable it | ||
| resource "restapi_object" "enable_cspm" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
maybe change the name of the resource since it will also support disabling cspm
| resource "restapi_object" "enable_cspm" { | |
| resource "restapi_object" "cspm" { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in order to unblock this PR, can you temporarily add the resource to the IgnoreAdds in test options and create a GIT issue to debug?
I suggest we add it to the module and DA documentation as a known issue
|
/run pipeline |
tests/pr_test.go
Outdated
| DeleteWorkspaceOnFail: false, | ||
| WaitJobCompleteMinutes: 60, | ||
| IgnoreUpdates: testhelper.Exemptions{ | ||
| List: []string{"module.scc_wp.restapi_object.enable_cspm"}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will be needed in all tests that enable CSPM. Also please link to a git issue tracking the problem. And add a note in both module and DA readmes
|
/run pipeline |
tests/pr_test.go
Outdated
| DeleteWorkspaceOnFail: false, | ||
| WaitJobCompleteMinutes: 60, | ||
| // workaround for https://github.com/terraform-ibm-modules/terraform-ibm-scc-workload-protection/issues/243 | ||
| IgnoreUpdates: testhelper.Exemptions{ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Its not an update, its a create, so need to use IgnoreAdds
|
/run pipeline |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Module and DA readme note still missing
|
/run pipeline |
|
While testing the DA through the catalog tile (and so through schematics), I'm getting the error: This is off as schematics runtime should have access to this private endpoint. I have reached out to the schematics team. For now, I'm going to default it back to public endpoint |
|
/run pipeline |
|
🎉 This PR is included in version 1.6.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