API calls for all endpoints tagged Content

API calls for all endpoints tagged Inspect

API calls for all endpoints tagged RootCategories

Handle Tesla connections for GoogleApi.DLP.V2beta1

Helper functions for deserializing responses into models

The request message for Operations.CancelOperation

The response message for Operations.ListOperations

This resource represents a long-running operation that is the result of a network API call

Options defining BigQuery table and row identifiers

Message defining the location of a BigQuery table. A table is uniquely identified by its project_id, dataset_id, and table_name. Within a query a table is often referenced with a string in the format of: `<project_id>:<dataset_id>.<table_id>` or `<project_id>.<dataset_id>.<table_id>`

Info Type Category description

Record key for a finding in a Cloud Storage file

Options defining a file or a set of files (path ending with *) within a Google Cloud Storage bucket

A location in Cloud Storage

Represents a color in the RGB color space

Container structure for the content to inspect

Request for scheduling a scan of a data subset from a Google Platform data repository

Record key for a finding in Cloud Datastore

Options defining a data set within Google Cloud Datastore

General identifier of a data field in a storage service

Set of files to scan

Container structure describing a single finding within a string or image

Bounding box encompassing detected text within an image

Configuration for determing how redaction of images should occur

Type of information detected by the API

Info type description

Max findings configuration per info type, per content item or long running operation

Statistics regarding a specific InfoType

Configuration description of the scanning process. When used with redactContent only info_types and min_likelihood are currently used

Request to search for potentially sensitive info in a list of items

Results of inspecting a list of items

Metadata returned within GetOperation for an inspect request

The operational data

All the findings for a single scanned item

A unique identifier for a Datastore entity. If a key's partition ID or any of its path kinds or names are reserved/read-only, the key is reserved/read-only. A reserved/read-only key is forbidden in certain documented contexts

A representation of a Datastore kind

Response to the ListInfoTypes request

Response to the ListInspectFindings request

Response for ListRootCategories request

Specifies the location of a finding within its source item

Additional configuration for inspect long running operations

Cloud repository for storing output

Datastore partition ID. A partition ID identifies a grouping of entities. The grouping is always by project and namespace, however the namespace ID may be empty. A partition ID contains several dimensions: project ID and namespace ID

A (kind, ID/name) pair used to construct a key path. If either name or ID is set, the element is complete. If neither is set, the element is incomplete

A representation of a Datastore property in a projection

A reference to a property relative to the Datastore kind expressions

Generic half-open interval [start, end)

Message for a unique key indicating a record that contains a finding

Request to search for potentially sensitive info in a list of items and replace it with a default or provided content

Results of redacting a list of items

Shared message indicating Cloud storage type

Structured content to inspect. Up to 50,000 `Value`s per request allowed

Location of a finding within a `ContentItem.Table`

Set of primitive values supported by the system

A generic empty message that you can re-use to avoid defining duplicated empty messages in your APIs. A typical example is to use it as the request or the response type of an API method. For instance: service Foo { rpc Bar(google.protobuf.Empty) returns (google.protobuf.Empty); } The JSON representation for `Empty` is empty JSON object `{}`

The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by gRPC. The error model is designed to be: - Simple to use and understand for most users - Flexible enough to meet unexpected needs # Overview The `Status` message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package `google.rpc` that can be used for common error conditions. # Language mapping The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the `Status` message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client, it may embed the `Status` in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting. - Batch operations. If a client uses batch request and batch response, the `Status` message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the `Status` message. - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons

Represents a whole calendar date, e.g. date of birth. The time of day and time zone are either specified elsewhere or are not significant. The date is relative to the Proleptic Gregorian Calendar. The day may be 0 to represent a year and month where the day is not significant, e.g. credit card expiration date. The year may be 0 to represent a month and day independent of year, e.g. anniversary date. Related types are google.type.TimeOfDay and `google.protobuf.Timestamp`

Represents a time of day. The date and time zone are either not significant or are specified elsewhere. An API may choose to allow leap seconds. Related types are google.type.Date and `google.protobuf.Timestamp`

Helper functions for building Tesla requests