Method: projects.locations.storedInfoTypes.create

Creates a pre-built stored infoType to be used for inspection. See https://cloud.google.com/sensitive-data-protection/docs/creating-stored-infotypes to learn more.

HTTP request


The URLs use gRPC Transcoding syntax.

Path parameters

Parameters
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/{projectId}/locations/{locationId}
  • Projects scope, no location specified (defaults to global): projects/{projectId}
  • Organizations scope, location specified: organizations/{org_id}/locations/{locationId}
  • Organizations scope, no location specified (defaults to global): organizations/{org_id}

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

Authorization requires the following IAM permission on the specified resource parent:

  • dlp.storedInfoType.create

Request body

The request body contains data with the following structure:

JSON representation
{
  "config": {
    object (StoredInfoTypeConfig)
  },
  "storedInfoTypeId": string,
  "locationId": string
}
Fields
config

object (StoredInfoTypeConfig)

Required. Configuration of the storedInfoType to create.

storedInfoTypeId

string

The storedInfoType 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.

locationId

string

Deprecated. This field has no effect.

Response body

If successful, the response body contains a newly created instance of StoredInfoType.

Authorization scopes

Requires the following OAuth scope:

  • https://www.googleapis.com/auth/cloud-platform

For more information, see the Authentication Overview.