feat: configure sensitive data scanner#1
Conversation
|
Unclear why the uploads are failing in the checks. Could be because the repo is not yet public? |
jamesiarmes
left a comment
jamesiarmes
left a comment
There was a problem hiding this comment.
Is there a reason this repo is private? Our standard practice is to make these modules public, and private repos are difficult to integrate into pipelines as OpenTofu dependencies.
| lifecycle { | ||
| # Use this meta-argument to avoid disabling the group when modifying the | ||
| # `included_keyword_configuration` field | ||
| create_before_destroy = true | ||
| } | ||
| for_each = data.datadog_sensitive_data_scanner_standard_pattern.patterns |
There was a problem hiding this comment.
not: for_each should be the first line in this block, and lifecycle should be at the end.
Only private while the repo is being setup, before first contributions are in. I'll change it to public. |
|
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
3 participants
First pass at a standard configuration for Datadog's Sensitive Data Scanner feature.
Ticket: https://codeforamerica.atlassian.net/browse/DEV-178