Creates a DeidentifyTemplate for reusing frequently used configuration for de-identifying content, images, and storage. See https://cloud.google.com/sensitive-data-protection/docs/creating-templates-deid to learn more.
Scopes
You will need authorization for the https://www.googleapis.com/auth/cloud-platform scope to make a valid call.
If unset, the scope for this method defaults to https://www.googleapis.com/auth/cloud-platform.
You can set the scope for this method like this: dlp2 --scope <scope> organizations deidentify-templates-create ...
Required Scalar Argument
- <parent> (string)
- Required. Parent resource name. The format of this value varies depending on the scope of the request (project or organization) and whether you have specified a processing location: + Projects scope, location specified:
projects/
PROJECT_ID/locations/
LOCATION_ID + Projects scope, no location specified (defaults to global):projects/
PROJECT_ID + Organizations scope, location specified:organizations/
ORG_ID/locations/
LOCATION_ID + Organizations scope, no location specified (defaults to global):organizations/
ORG_ID The following exampleparent
string specifies a parent project with the identifierexample-project
, and specifies theeurope-west3
location for processing data: parent=projects/example-project/locations/europe-west3
- Required. Parent resource name. The format of this value varies depending on the scope of the request (project or organization) and whether you have specified a processing location: + Projects scope, location specified:
Required Request Value
The request value is a data-structure with various fields. Each field may be a simple scalar or another data-structure. In the latter case it is advised to set the field-cursor to the data-structure's field to specify values more concisely.
For example, a structure like this:
GooglePrivacyDlpV2CreateDeidentifyTemplateRequest:
deidentify-template:
create-time: string
description: string
display-name: string
name: string
update-time: string
location-id: string
template-id: string
can be set completely with the following arguments which are assumed to be executed in the given order. Note how the cursor position is adjusted to the respective structures, allowing simple field names to be used most of the time.
-r .deidentify-template create-time=et
- Output only. The creation timestamp of an inspectTemplate.
description=magna
- Short description (max 256 chars).
display-name=no
- Display name (max 256 chars).
name=ipsum
- Output only. The template name. The template will have one of the following formats:
projects/PROJECT_ID/deidentifyTemplates/TEMPLATE_ID
ORorganizations/ORGANIZATION_ID/deidentifyTemplates/TEMPLATE_ID
- Output only. The template name. The template will have one of the following formats:
-
update-time=voluptua.
- Output only. The last update timestamp of an inspectTemplate.
-
.. location-id=at
- Deprecated. This field has no effect.
template-id=sanctus
- The template id can contain uppercase and lowercase letters, numbers, and hyphens; that is, it must match the regular expression:
[a-zA-Z\d-_]+
. The maximum length is 100 characters. Can be empty to allow the system to generate one.
- The template id can contain uppercase and lowercase letters, numbers, and hyphens; that is, it must match the regular expression:
About Cursors
The cursor position is key to comfortably set complex nested structures. The following rules apply:
- The cursor position is always set relative to the current one, unless the field name starts with the
.
character. Fields can be nested such as in-r f.s.o
. - The cursor position is set relative to the top-level structure if it starts with
.
, e.g.-r .s.s
- You can also set nested fields without setting the cursor explicitly. For example, to set a value relative to the current cursor position, you would specify
-r struct.sub_struct=bar
. - You can move the cursor one level up by using
..
. Each additional.
moves it up one additional level. E.g....
would go three levels up.
Optional Output Flags
The method's return value a JSON encoded structure, which will be written to standard output by default.
- -o out
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
-
to indicate standard output, or a filepath that is to contain the received bytes. If unset, it defaults to standard output.
- out specifies the destination to which to write the server's result to.
It will be a JSON-encoded structure.
The destination may be
Optional General Properties
The following properties can configure any call, and are not specific to this method.
-
-p $-xgafv=string
- V1 error format.
-
-p access-token=string
- OAuth access token.
-
-p alt=string
- Data format for response.
-
-p callback=string
- JSONP
-
-p fields=string
- Selector specifying which fields to include in a partial response.
-
-p key=string
- API key. Your API key identifies your project and provides you with API access, quota, and reports. Required unless you provide an OAuth 2.0 token.
-
-p oauth-token=string
- OAuth 2.0 token for the current user.
-
-p pretty-print=boolean
- Returns response with indentations and line breaks.
-
-p quota-user=string
- Available to use for quota purposes for server-side applications. Can be any arbitrary string assigned to a user, but should not exceed 40 characters.
-
-p upload-type=string
- Legacy upload protocol for media (e.g. "media", "multipart").
-
-p upload-protocol=string
- Upload protocol for media (e.g. "raw", "multipart").