Skip to content
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

google_scc_mute_config support #13610

Comments

@drandell
Copy link
Contributor

drandell commented Jan 31, 2023

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment. If the issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If the issue is assigned to a user, that user is claiming responsibility for the issue. If the issue is assigned to "hashibot", a community member has claimed the issue already.

Description

Support for creating mute configs in SCC:
https://cloud.google.com/security-command-center/docs/reference/rest/v1/organizations.muteConfigs/create

New or Affected Resource(s)

  • google_scc_mute_config

Potential Terraform Configuration

resource "google_scc_mute_config" "my_config" {
  config_id    = "my-config"
  organisation = "12345678"
  description = "My Awesome Mute Config"
  filter = "severity=LOW"
}

Curious as to why the current notification config is only supported at the org level? Even though the parent config can exist at folder or project level? (Same applies here)

References

  • #0000
@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.