Marketplace
BrowsePublish
Marketplace
You are viewing an outdated version of provider-gcp.Go to Latest
upbound/provider-gcp@v0.41.2
JobTrigger
datalossprevention.gcp.upbound.io
JobTrigger
upbound/provider-gcp@v0.41.2datalossprevention.gcp.upbound.io

JobTrigger is the Schema for the JobTriggers API. A job trigger configuration.

Type

CRD

Group

datalossprevention.gcp.upbound.io

Version

v1beta1

apiVersion: datalossprevention.gcp.upbound.io/v1beta1

kind: JobTrigger

API Documentation
apiVersion
string
kind
string
metadata
object
spec
object
object

JobTriggerSpec defines the desired state of JobTrigger

forProvider
requiredobject
requiredobject

No description provided.

array

Controls what and how to inspect for findings. Structure is documented below.

actions
array
array

A task to execute on the completion of a job. Structure is documented below.

array

Create a de-identified copy of the requested table or files. Structure is documented below.

array

List of user-specified file type groups to transform. If specified, only the files with these filetypes will be transformed. If empty, all supported files will be transformed. Supported types may be automatically added over time. If a file type is set in this field that isn't supported by the Deidentify action then the job will fail and will not be successfully created/started. Each value may be one of: IMAGE, TEXT_FILE, CSV, TSV.

array

User specified deidentify templates and configs for structured, unstructured, and image files. Structure is documented below.

array

Config for storing transformation details. Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
object

Reference to a Dataset in bigquery to populate datasetId.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Dataset in bigquery to populate datasetId.

policy
object
object

Policies for selection.

resolve
string
projectId
string
tableId
string
object

Reference to a Table in bigquery to populate tableId.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Table in bigquery to populate tableId.

policy
object
object

Policies for selection.

resolve
string
array

Sends an email when the job completes. The email goes to IAM project owners and technical Essential Contacts.

pubSub
array
array

Publish a message into a given Pub/Sub topic when the job completes. Structure is documented below.

topic
string
array

Publish findings of a DlpJob to Data Catalog.

array

Publish the result summary of a DlpJob to the Cloud Security Command Center.

array

Enable Stackdriver metric dlp.googleapis.com/findingCount.

array

If set, the detailed findings will be persisted to the specified OutputStorageConfig. Only a single instance of this action can be specified. Compatible with: Inspect, Risk Structure is documented below.

array

Information on where to store output Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

The core content of the template. Structure is documented below.

array

Custom info types to be used. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
array

A reference to a StoredInfoType to use with scanning. Structure is documented below.

name
string
array

Message for detecting output from deidentification transformations that support reversing.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
limits
array
array

Configuration to control the number of findings returned. Structure is documented below.

array

Configuration of findings limit given for specified infoTypes. Structure is documented below.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
ruleSet
array
array

Set of rules to apply to the findings for this InspectConfig. Exclusion rules, contained in the set are executed in the end, other rules are executed in the order they are specified for each info type. Structure is documented below.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
rules
array
array

Set of rules to be applied to infoTypes. The rules are applied in order. Structure is documented below.

array

The rule that specifies conditions when findings of infoTypes specified in InspectionRuleSet are removed from results. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Drop if the hotword rule is contained in the proximate context. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

When true, excludes type information of the findings.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Hotword-based detection rule. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Likelihood adjustment to apply to all matching findings. Structure is documented below.

array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

Information on where to inspect Structure is documented below.

array

Options defining BigQuery table and row identifiers. Structure is documented below.

array

References to fields excluded from scanning. This allows you to skip inspection of entire columns which you know have no findings. Structure is documented below.

name
string
array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Limit scanning only to these fields. Structure is documented below.

name
string
rowsLimit
number
array

Set of files to scan. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

Options defining a file or a set of files within a Google Cloud Storage bucket. Structure is documented below.

fileSet
array
array

Set of files to scan. Structure is documented below.

array

The regex-filtered set of files to scan. Structure is documented below.

array

A list of regular expressions matching file paths to exclude. All files in the bucket that match at least one of these regular expressions will be excluded from the scan.

array

A list of regular expressions matching file paths to include. All files in the bucket that match at least one of these regular expressions will be included in the set of files, except for those that also match an item in excludeRegex. Leaving this field empty will match all files by default (this is equivalent to including .* in the list)

url
string
array

List of file type groups to include in the scan. If empty, all files are scanned and available data format processors are applied. In addition, the binary content of the selected files is always scanned as well. Images are scanned only as binary if the specified region does not support image inspection and no fileTypes were specified. Each value may be one of: BINARY_FILE, TEXT_FILE, IMAGE, WORD, PDF, AVRO, CSV, TSV, POWERPOINT, EXCEL.

array

Options defining a data set within Google Cloud Datastore. Structure is documented below.

kind
array
array

A representation of a Datastore kind. Structure is documented below.

name
string
array

Datastore partition ID. A partition ID identifies a grouping of entities. The grouping is always by project and namespace, however the namespace ID may be empty. Structure is documented below.

array

Configuration to control jobs where the content being inspected is outside of Google Cloud Platform. Structure is documented below.

labels
object
array

These are labels that each inspection request must include within their 'finding_labels' map. Request may contain others, but any missing one of these will be rejected. Label keys must be between 1 and 63 characters long and must conform to the following regular expression: a-z?. No more than 10 keys can be required.

array

If the container is a table, additional information to make findings meaningful such as the columns that are primary keys. Structure is documented below.

array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Information on where to inspect Structure is documented below.

endTime
string
startTime
string
array

Information on where to inspect Structure is documented below.

name
string
parent
string
status
string
triggerId
string
array

What event needs to occur for a new job to be started. Structure is documented below.

manual
array
array

For use with hybrid jobs. Jobs must be manually created and finished.

array

Schedule for triggered jobs Structure is documented below.

object

THIS IS A BETA FIELD. It will be honored unless the Management Policies feature flag is disabled. InitProvider holds the same fields as ForProvider, with the exception of Identifier and other resource reference fields. The fields that are in InitProvider are merged into ForProvider when the resource is created. The same fields are also added to the terraform ignore_changes hook, to avoid updating them after creation. This is useful for fields that are required on creation, but we do not desire to update them after creation, for example because of an external controller is managing them, like an autoscaler.

array

Controls what and how to inspect for findings. Structure is documented below.

actions
array
array

A task to execute on the completion of a job. Structure is documented below.

array

Create a de-identified copy of the requested table or files. Structure is documented below.

array

List of user-specified file type groups to transform. If specified, only the files with these filetypes will be transformed. If empty, all supported files will be transformed. Supported types may be automatically added over time. If a file type is set in this field that isn't supported by the Deidentify action then the job will fail and will not be successfully created/started. Each value may be one of: IMAGE, TEXT_FILE, CSV, TSV.

array

User specified deidentify templates and configs for structured, unstructured, and image files. Structure is documented below.

array

Config for storing transformation details. Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
object

Reference to a Dataset in bigquery to populate datasetId.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Dataset in bigquery to populate datasetId.

policy
object
object

Policies for selection.

resolve
string
projectId
string
tableId
string
object

Reference to a Table in bigquery to populate tableId.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

Selector for a Table in bigquery to populate tableId.

policy
object
object

Policies for selection.

resolve
string
array

Sends an email when the job completes. The email goes to IAM project owners and technical Essential Contacts.

pubSub
array
array

Publish a message into a given Pub/Sub topic when the job completes. Structure is documented below.

topic
string
array

Publish findings of a DlpJob to Data Catalog.

array

Publish the result summary of a DlpJob to the Cloud Security Command Center.

array

Enable Stackdriver metric dlp.googleapis.com/findingCount.

array

If set, the detailed findings will be persisted to the specified OutputStorageConfig. Only a single instance of this action can be specified. Compatible with: Inspect, Risk Structure is documented below.

array

Information on where to store output Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

The core content of the template. Structure is documented below.

array

Custom info types to be used. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
array

A reference to a StoredInfoType to use with scanning. Structure is documented below.

name
string
array

Message for detecting output from deidentification transformations that support reversing.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
limits
array
array

Configuration to control the number of findings returned. Structure is documented below.

array

Configuration of findings limit given for specified infoTypes. Structure is documented below.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
ruleSet
array
array

Set of rules to apply to the findings for this InspectConfig. Exclusion rules, contained in the set are executed in the end, other rules are executed in the order they are specified for each info type. Structure is documented below.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
rules
array
array

Set of rules to be applied to infoTypes. The rules are applied in order. Structure is documented below.

array

The rule that specifies conditions when findings of infoTypes specified in InspectionRuleSet are removed from results. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Drop if the hotword rule is contained in the proximate context. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

When true, excludes type information of the findings.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Hotword-based detection rule. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Likelihood adjustment to apply to all matching findings. Structure is documented below.

array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

Information on where to inspect Structure is documented below.

array

Options defining BigQuery table and row identifiers. Structure is documented below.

array

References to fields excluded from scanning. This allows you to skip inspection of entire columns which you know have no findings. Structure is documented below.

name
string
array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Limit scanning only to these fields. Structure is documented below.

name
string
rowsLimit
number
array

Set of files to scan. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

Options defining a file or a set of files within a Google Cloud Storage bucket. Structure is documented below.

fileSet
array
array

Set of files to scan. Structure is documented below.

array

The regex-filtered set of files to scan. Structure is documented below.

array

A list of regular expressions matching file paths to exclude. All files in the bucket that match at least one of these regular expressions will be excluded from the scan.

array

A list of regular expressions matching file paths to include. All files in the bucket that match at least one of these regular expressions will be included in the set of files, except for those that also match an item in excludeRegex. Leaving this field empty will match all files by default (this is equivalent to including .* in the list)

url
string
array

List of file type groups to include in the scan. If empty, all files are scanned and available data format processors are applied. In addition, the binary content of the selected files is always scanned as well. Images are scanned only as binary if the specified region does not support image inspection and no fileTypes were specified. Each value may be one of: BINARY_FILE, TEXT_FILE, IMAGE, WORD, PDF, AVRO, CSV, TSV, POWERPOINT, EXCEL.

array

Options defining a data set within Google Cloud Datastore. Structure is documented below.

kind
array
array

A representation of a Datastore kind. Structure is documented below.

name
string
array

Datastore partition ID. A partition ID identifies a grouping of entities. The grouping is always by project and namespace, however the namespace ID may be empty. Structure is documented below.

array

Configuration to control jobs where the content being inspected is outside of Google Cloud Platform. Structure is documented below.

labels
object
array

These are labels that each inspection request must include within their 'finding_labels' map. Request may contain others, but any missing one of these will be rejected. Label keys must be between 1 and 63 characters long and must conform to the following regular expression: a-z?. No more than 10 keys can be required.

array

If the container is a table, additional information to make findings meaningful such as the columns that are primary keys. Structure is documented below.

array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Information on where to inspect Structure is documented below.

endTime
string
startTime
string
array

Information on where to inspect Structure is documented below.

name
string
parent
string
status
string
triggerId
string
array

What event needs to occur for a new job to be started. Structure is documented below.

manual
array
array

For use with hybrid jobs. Jobs must be manually created and finished.

array

Schedule for triggered jobs Structure is documented below.

array

THIS IS A BETA FIELD. It is on by default but can be opted out through a Crossplane feature flag. ManagementPolicies specify the array of actions Crossplane is allowed to take on the managed and external resources. This field is planned to replace the DeletionPolicy field in a future release. Currently, both could be set independently and non-default values would be honored if the feature flag is enabled. If both are custom, the DeletionPolicy field will be ignored. See the design doc for more information: https://github.com/crossplane/crossplane/blob/499895a25d1a1a0ba1604944ef98ac7a1a71f197/design/design-doc-observe-only-resources.md?plain=1#L223 and this one: https://github.com/crossplane/crossplane/blob/444267e84783136daa93568b364a5f01228cacbe/design/one-pager-ignore-changes.md

object

ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
object

PublishConnectionDetailsTo specifies the connection secret config which contains a name, metadata and a reference to secret store config to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource.

configRef
object
object

SecretStoreConfigRef specifies which secret store config should be used for this ConnectionSecret.

name
requiredstring
policy
object
object

Policies for referencing.

resolve
string
metadata
object
object

Metadata is the metadata for connection secret.

labels
object
type
string
name
requiredstring
object

WriteConnectionSecretToReference specifies the namespace and name of a Secret to which any connection details for this managed resource should be written. Connection details frequently include the endpoint, username, and password required to connect to the managed resource. This field is planned to be replaced in a future release in favor of PublishConnectionDetailsTo. Currently, both could be set independently and connection details would be published to both without affecting each other.

name
requiredstring
namespace
requiredstring
status
object
object

JobTriggerStatus defines the observed state of JobTrigger.

object

No description provided.

id
string
array

Controls what and how to inspect for findings. Structure is documented below.

actions
array
array

A task to execute on the completion of a job. Structure is documented below.

array

Create a de-identified copy of the requested table or files. Structure is documented below.

array

List of user-specified file type groups to transform. If specified, only the files with these filetypes will be transformed. If empty, all supported files will be transformed. Supported types may be automatically added over time. If a file type is set in this field that isn't supported by the Deidentify action then the job will fail and will not be successfully created/started. Each value may be one of: IMAGE, TEXT_FILE, CSV, TSV.

array

User specified deidentify templates and configs for structured, unstructured, and image files. Structure is documented below.

array

Config for storing transformation details. Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

Sends an email when the job completes. The email goes to IAM project owners and technical Essential Contacts.

pubSub
array
array

Publish a message into a given Pub/Sub topic when the job completes. Structure is documented below.

topic
string
array

Publish findings of a DlpJob to Data Catalog.

array

Publish the result summary of a DlpJob to the Cloud Security Command Center.

array

Enable Stackdriver metric dlp.googleapis.com/findingCount.

array

If set, the detailed findings will be persisted to the specified OutputStorageConfig. Only a single instance of this action can be specified. Compatible with: Inspect, Risk Structure is documented below.

array

Information on where to store output Structure is documented below.

table
array
array

The BigQuery table in which to store the output. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

The core content of the template. Structure is documented below.

array

Custom info types to be used. See https://cloud.google.com/dlp/docs/creating-custom-infotypes to learn more. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
array

A reference to a StoredInfoType to use with scanning. Structure is documented below.

name
string
array

Message for detecting output from deidentification transformations that support reversing.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
limits
array
array

Configuration to control the number of findings returned. Structure is documented below.

array

Configuration of findings limit given for specified infoTypes. Structure is documented below.

array

Type of information the findings limit applies to. Only one limit per infoType should be provided. If InfoTypeLimit does not have an infoType, the DLP API applies the limit against all infoTypes that are found but not specified in another InfoTypeLimit. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
ruleSet
array
array

Set of rules to apply to the findings for this InspectConfig. Exclusion rules, contained in the set are executed in the end, other rules are executed in the order they are specified for each info type. Structure is documented below.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
rules
array
array

Set of rules to be applied to infoTypes. The rules are applied in order. Structure is documented below.

array

The rule that specifies conditions when findings of infoTypes specified in InspectionRuleSet are removed from results. Structure is documented below.

array

Dictionary which defines the rule. Structure is documented below.

array

Newline-delimited file of words in Cloud Storage. Only a single file is accepted. Structure is documented below.

path
string
array

List of words or phrases to search for. Structure is documented below.

words
array
array

Words or phrases defining the dictionary. The dictionary must contain at least one phrase and every phrase must contain at least 2 characters that are letters or digits.

array

Drop if the hotword rule is contained in the proximate context. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

When true, excludes type information of the findings.

array

List of infoTypes this rule set is applied to. Structure is documented below.

name
string
array

Optional custom sensitivity for this InfoType. This only applies to data profiling. Structure is documented below.

score
string
version
string
regex
array
array

Regular expression which defines the rule. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Hotword-based detection rule. Structure is documented below.

array

Regular expression pattern defining what qualifies as a hotword. Structure is documented below.

array

The index of the submatch to extract as findings. When not specified, the entire match is returned. No more than 3 may be included.

pattern
string
array

Likelihood adjustment to apply to all matching findings. Structure is documented below.

array

Proximity of the finding within which the entire hotword must reside. The total length of the window cannot exceed 1000 characters. Note that the finding itself will be included in the window, so that hotwords may be used to match substrings of the finding itself. For example, the certainty of a phone number regex (\d{3}) \d{3}-\d{4} could be adjusted upwards if the area code is known to be the local area code of a company office using the hotword regex (xxx), where xxx is the area code in question. Structure is documented below.

array

Information on where to inspect Structure is documented below.

array

Options defining BigQuery table and row identifiers. Structure is documented below.

array

References to fields excluded from scanning. This allows you to skip inspection of entire columns which you know have no findings. Structure is documented below.

name
string
array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Limit scanning only to these fields. Structure is documented below.

name
string
rowsLimit
number
array

Set of files to scan. Structure is documented below.

datasetId
string
projectId
string
tableId
string
array

Options defining a file or a set of files within a Google Cloud Storage bucket. Structure is documented below.

fileSet
array
array

Set of files to scan. Structure is documented below.

array

The regex-filtered set of files to scan. Structure is documented below.

array

A list of regular expressions matching file paths to exclude. All files in the bucket that match at least one of these regular expressions will be excluded from the scan.

array

A list of regular expressions matching file paths to include. All files in the bucket that match at least one of these regular expressions will be included in the set of files, except for those that also match an item in excludeRegex. Leaving this field empty will match all files by default (this is equivalent to including .* in the list)

url
string
array

List of file type groups to include in the scan. If empty, all files are scanned and available data format processors are applied. In addition, the binary content of the selected files is always scanned as well. Images are scanned only as binary if the specified region does not support image inspection and no fileTypes were specified. Each value may be one of: BINARY_FILE, TEXT_FILE, IMAGE, WORD, PDF, AVRO, CSV, TSV, POWERPOINT, EXCEL.

array

Options defining a data set within Google Cloud Datastore. Structure is documented below.

kind
array
array

A representation of a Datastore kind. Structure is documented below.

name
string
array

Datastore partition ID. A partition ID identifies a grouping of entities. The grouping is always by project and namespace, however the namespace ID may be empty. Structure is documented below.

array

Configuration to control jobs where the content being inspected is outside of Google Cloud Platform. Structure is documented below.

labels
object
array

These are labels that each inspection request must include within their 'finding_labels' map. Request may contain others, but any missing one of these will be rejected. Label keys must be between 1 and 63 characters long and must conform to the following regular expression: a-z?. No more than 10 keys can be required.

array

If the container is a table, additional information to make findings meaningful such as the columns that are primary keys. Structure is documented below.

array

The columns that are the primary keys for table objects included in ContentItem. A copy of this cell's value will stored alongside alongside each finding so that the finding can be traced to the specific row it came from. No more than 3 may be provided. Structure is documented below.

name
string
array

Information on where to inspect Structure is documented below.

endTime
string
startTime
string
array

Information on where to inspect Structure is documented below.

name
string
name
string
parent
string
status
string
triggerId
string
array

What event needs to occur for a new job to be started. Structure is documented below.

manual
array
array

For use with hybrid jobs. Jobs must be manually created and finished.

array

Schedule for triggered jobs Structure is documented below.

array

Conditions of the resource.

lastTransitionTime
requiredstring
message
string
reason
requiredstring
status
requiredstring
type
requiredstring
Marketplace

Discover the building blocks for your internal cloud platform.

© 2022 Upbound, Inc.

SolutionsProvidersConfigurations
LearnDocumentationTry for Free
MorePrivacy PolicyTerms & Conditions
Marketplace

© 2022 Upbound, Inc.

Marketplace

Discover the building blocksfor your internal cloud platform.