Template to use. Any configuration directly specified in
inspect_config will override those set in the template. Singular fields
that are set in this request will replace their corresponding fields in the
template. Repeated fields are appended. Singular sub-messages and groups
are recursively merged.
Template to use. Any configuration directly specified in
inspect_config will override those set in the template. Singular fields
that are set in this request will replace their corresponding fields in the
template. Repeated fields are appended. Singular sub-messages and groups
are recursively merged.
Projects scope, no location specified (defaults to global):<br/>
projects/<var>PROJECT_ID</var>
The following example parent string specifies a parent project with the
identifier example-project, and specifies the europe-west3 location
for processing data:
parent=projects/example-project/locations/europe-west3
Projects scope, no location specified (defaults to global):<br/>
projects/<var>PROJECT_ID</var>
The following example parent string specifies a parent project with the
identifier example-project, and specifies the europe-west3 location
for processing data:
parent=projects/example-project/locations/europe-west3
Configuration for the re-identification of the content item.
This field shares the same proto message type that is used for
de-identification, however its usage here is for the reversal of the
previous de-identification. Re-identification is performed by examining
the transformations used to de-identify the items and executing the
reverse. This requires that only reversible transformations
be provided here. The reversible transformations are:
Configuration for the re-identification of the content item.
This field shares the same proto message type that is used for
de-identification, however its usage here is for the reversal of the
previous de-identification. Re-identification is performed by examining
the transformations used to de-identify the items and executing the
reverse. This requires that only reversible transformations
be provided here. The reversible transformations are:
Template to use. References an instance of DeidentifyTemplate.
Any configuration directly specified in reidentify_config or
inspect_config will override those set in the template. The
DeidentifyTemplate used must include only reversible transformations.
Singular fields that are set in this request will replace their
corresponding fields in the template. Repeated fields are appended.
Singular sub-messages and groups are recursively merged.
Template to use. References an instance of DeidentifyTemplate.
Any configuration directly specified in reidentify_config or
inspect_config will override those set in the template. The
DeidentifyTemplate used must include only reversible transformations.
Singular fields that are set in this request will replace their
corresponding fields in the template. Repeated fields are appended.
Singular sub-messages and groups are recursively merged.
Configuration for the re-identification of the content item.
This field shares the same proto message type that is used for
de-identification, however its usage here is for the reversal of the
previous de-identification. Re-identification is performed by examining
the transformations used to de-identify the items and executing the
reverse. This requires that only reversible transformations
be provided here. The reversible transformations are:
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-01-28 UTC."],[],[]]
