Namespace Google.Apis.CCAIPlatform.v1alpha1.Data

Classes

AdminUser

Message storing info about the first admin user. Next ID: 3

CancelOperationRequest

The request message for Operations.CancelOperation.

Component

Defines a logical CCAIP component that e.g. “EMAIL”, "CRM". For more information see go/ccaip-private-path-v2. Each logical component is associated with a list of service attachments.

Critical

Instances in this Channel will receive updates after all instances in Normal were updated. They also will only be updated outside of their peak hours.

Early

LINT.IfChange First Channel to receive the updates. Meant to dev/test instances

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); }

GoogleCloudCommonOperationMetadata

Represents the metadata of the long-running operation.

InstanceConfig

Message storing the instance configuration.

ListContactCentersResponse

Message for response to listing ContactCenters

ListLocationsResponse

The response message for Locations.ListLocations.

ListOperationsResponse

The response message for Operations.ListOperations.

Location

A resource that represents a Google Cloud location.

Normal

Instances in this Channel will receive updates after all instances in Early were updated + 2 days.

Operation

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

OperationMetadata

Represents the metadata of the long-running operation.

PrivateAccess

Defines ingress and egress private traffic settings for CCAIP instances.

PscSetting

Private service connect settings.

Quota

Quota details.

SAMLParams

Message storing SAML params to enable Google as IDP.

Status

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. Each Status message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the API Design Guide.