Skip to content

Add support for notification_report argument in post scan actions block of dataplex data quality scan #22068

Open
@ematala

Description

@ematala

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 an issue is assigned to a user, that user is claiming responsibility for the issue.
  • Customers working with a Google Technical Account Manager or Customer Engineer can ask them to reach out internally to expedite investigation and resolution of this issue.

Description

As a user of Dataplex, I want to be notified about (failed) data quality scans via email.

The Dataplex REST API allows to pass a notificationReport argument inside the postScanActions object to configure email notifications like so:

{
  "postScanActions": {
    "notificationReport": {
      "recipients": {
        "emails": ["[email protected]"]
      },
      "scoreThresholdTrigger": {
        "scoreThreshold": 42
      },
      // or "jobFailureTrigger": {},
      // or "jobEndTrigger": {}
    }
  }
}

In order to use this feature inside a Terraform configuration, it would be great if it was possible to pass the notification_report argument into the post_scan_actions block which currently only supports the bigquery_export argument.

New or Affected Resource(s)

  • google_dataplex_datascan

Potential Terraform Configuration

resource "google_dataplex_datascan" "auto_data_quality_scan" {
  data_quality_spec {
    post_scan_actions {
      notification_report {
        recipients {
          emails = ["[email protected]"]
        }
        score_threshold_trigger {
          score_threshold = 42
        }
        # or job_failure_trigger {}
        # or job_end_trigger {}
      }
    }
  }
}

References

b/406869591

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions