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
JobTriggerSpec defines the desired state of JobTrigger
No description provided.
Controls what and how to inspect for findings. Structure is documented below.
A task to execute on the completion of a job. Structure is documented below.
Publish a message into a given Pub/Sub topic when the job completes. Structure is documented below.
Publish findings of a DlpJob to Data Catalog.
Publish the result summary of a DlpJob to the Cloud Security Command Center.
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.
Information on where to store output Structure is documented below.
Information on where to inspect Structure is documented below.
Options defining BigQuery table and row identifiers. Structure is documented below.
Specifies the BigQuery fields that will be returned with findings. If not specified, no identifying fields will be returned for findings. Structure is documented below.
Options defining a file or a set of files within a Google Cloud Storage bucket. Structure is documented below.
Set of files to scan. Structure is documented below.
The regex-filtered set of files to scan. Structure is documented below.
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.
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)
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, and TSV.
Options defining a data set within Google Cloud Datastore. Structure is documented below.
A representation of a Datastore kind. Structure is documented below.
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.
Information on where to inspect Structure is documented below.
Information on where to inspect Structure is documented below.
What event needs to occur for a new job to be started. Structure is documented below.
Schedule for triggered jobs Structure is documented below.
ProviderConfigReference specifies how the provider that will be used to create, observe, update, and delete this managed resource should be configured.
Policies for referencing.
ProviderReference specifies the provider that will be used to create, observe, update, and delete this managed resource. Deprecated: Please use ProviderConfigReference, i.e. providerConfigRef
Policies for referencing.
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.
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.
JobTriggerStatus defines the observed state of JobTrigger.
No description provided.
Conditions of the resource.
basic
apiVersion: datalossprevention.gcp.upbound.io/v1beta1
kind: JobTrigger
metadata:
annotations:
meta.upbound.io/example-id: datalossprevention/v1beta1/jobtrigger
upjet.upbound.io/manual-intervention: The resource requires a real Project ID
labels:
testing.upbound.io/example-name: basic
name: basic
spec:
forProvider:
description: Description
displayName: Displayname
inspectJob:
- actions:
- saveFindings:
- outputConfig:
- table:
- datasetId: dataset
projectId: project
inspectTemplateName: fake
storageConfig:
- cloudStorageOptions:
- fileSet:
- url: gs://mybucket/directory/
parent: projects/&{project_id}
triggers:
- schedule:
- recurrencePeriodDuration: 86400s
© 2022 Upbound, Inc.
Discover the building blocksfor your internal cloud platform.