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

Add Support for DLP Resources #3898

Comments

@abombss
Copy link

abombss commented Jun 21, 2019

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

We would like support for Data Loss Prevention so we can auto-enable and manage DLP job scans for GCP resources.

New or Affected Resource(s)

Potential Terraform Configuration

References

https://cloud.google.com/dlp/docs/reference/rest/

@ghost ghost added the enhancement label Jun 21, 2019
@paddycarver paddycarver added this to the Goals milestone Dec 6, 2019
@danawillow
Copy link
Contributor

We're looking at adding this to our roadmap, but would like some clarity on use cases and priorities since some of these resources are quite large. If anyone who's subscribed to this could give an overview of which resources they would use in Terraform and how they would configure them, that would be a big help.

@nat-henderson
Copy link
Contributor

I'll be consulting with the team next week, so we can gather the right information and add this to our roadmap at our next sprint planning meeting, a week from next monday.

@nat-henderson
Copy link
Contributor

Great!

We will want to start with the Trigger resource, which depends on the Template resources (both Inspect and Deidentify, with Inspect being marginally more important). Slightly less crucial (but still mandatory) is the stored info type.

Project and org resources can safely be combined into one multiparent resource.

We'll discuss in our next sprint planning meeting.

@ghost
Copy link

ghost commented Oct 29, 2020

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked as resolved and limited conversation to collaborators Oct 29, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.