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

InspectTemplate is the Schema for the InspectTemplates API. An inspect job template.

Type

CRD

Group

datalossprevention.gcp.upbound.io

Version

v1beta1

apiVersion: datalossprevention.gcp.upbound.io/v1beta1

kind: InspectTemplate

API Documentation
apiVersion
string
kind
string
metadata
object
spec
object
object

InspectTemplateSpec defines the desired state of InspectTemplate

forProvider
requiredobject
requiredobject

No description provided.

array

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

array

List of options defining data content to scan. If empty, text, images, and other content will be included. Each value may be one of: CONTENT_TEXT, CONTENT_IMAGE.

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

Restricts what infoTypes to look for. The values must correspond to InfoType values returned by infoTypes.list or listed at https://cloud.google.com/dlp/docs/infotypes-reference. When no InfoTypes or CustomInfoTypes are specified in a request, the system may automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated. 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. For tabular data, the context includes the column name. 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.

parent
string
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

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

array

List of options defining data content to scan. If empty, text, images, and other content will be included. Each value may be one of: CONTENT_TEXT, CONTENT_IMAGE.

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

Restricts what infoTypes to look for. The values must correspond to InfoType values returned by infoTypes.list or listed at https://cloud.google.com/dlp/docs/infotypes-reference. When no InfoTypes or CustomInfoTypes are specified in a request, the system may automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated. 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. For tabular data, the context includes the column name. 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.

parent
string
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

InspectTemplateStatus defines the observed state of InspectTemplate.

object

No description provided.

id
string
array

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

array

List of options defining data content to scan. If empty, text, images, and other content will be included. Each value may be one of: CONTENT_TEXT, CONTENT_IMAGE.

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

Restricts what infoTypes to look for. The values must correspond to InfoType values returned by infoTypes.list or listed at https://cloud.google.com/dlp/docs/infotypes-reference. When no InfoTypes or CustomInfoTypes are specified in a request, the system may automatically choose what detectors to run. By default this may be all types, but may change over time as detectors are updated. 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. For tabular data, the context includes the column name. 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.

name
string
parent
string
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.