Reference documentation and code samples for the Data Loss Prevention V2 Client class HybridOptions.
Configuration to control jobs where the content being inspected is outside of Google Cloud Platform.
Generated from protobuf message google.privacy.dlp.v2.HybridOptions
Namespace
Google \ Cloud \ Dlp \ V2Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ description
string
A short description of where the data is coming from. Will be stored once in the job. 256 max length.
↳ required_finding_label_keys
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]([-a-z0-9]*[a-z0-9])?
. No more than 10 keys can be required.
↳ labels
array| Google\Protobuf\Internal\MapField
To organize findings, these labels will be added to each finding. Label keys must be between 1 and 63 characters long and must conform to the following regular expression: [a-z]([-a-z0-9]*[a-z0-9])?
. Label values must be between 0 and 63 characters long and must conform to the regular expression ([a-z]([-a-z0-9]*[a-z0-9])?)?
. No more than 10 labels can be associated with a given finding. Examples: * "environment" : "production"
* "pipeline" : "etl"
↳ table_options
Google\Cloud\Dlp\V2\TableOptions
If the container is a table, additional information to make findings meaningful such as the columns that are primary keys.
getDescription
A short description of where the data is coming from. Will be stored once in the job. 256 max length.
string
setDescription
A short description of where the data is coming from. Will be stored once in the job. 256 max length.
var
string
$this
getRequiredFindingLabelKeys
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]([-a-z0-9]*[a-z0-9])?
.
No more than 10 keys can be required.
setRequiredFindingLabelKeys
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]([-a-z0-9]*[a-z0-9])?
.
No more than 10 keys can be required.
var
string[]
$this
getLabels
To organize findings, these labels will be added to each finding.
Label keys must be between 1 and 63 characters long and must conform
to the following regular expression: [a-z]([-a-z0-9]*[a-z0-9])?
.
Label values must be between 0 and 63 characters long and must conform
to the regular expression ([a-z]([-a-z0-9]*[a-z0-9])?)?
.
No more than 10 labels can be associated with a given finding.
Examples:
-
"environment" : "production" -
"pipeline" : "etl"
setLabels
To organize findings, these labels will be added to each finding.
Label keys must be between 1 and 63 characters long and must conform
to the following regular expression: [a-z]([-a-z0-9]*[a-z0-9])?
.
Label values must be between 0 and 63 characters long and must conform
to the regular expression ([a-z]([-a-z0-9]*[a-z0-9])?)?
.
No more than 10 labels can be associated with a given finding.
Examples:
-
"environment" : "production" -
"pipeline" : "etl"
$this
getTableOptions
If the container is a table, additional information to make findings meaningful such as the columns that are primary keys.
hasTableOptions
clearTableOptions
setTableOptions
If the container is a table, additional information to make findings meaningful such as the columns that are primary keys.
$this
