Namespace Google.Apis.ManagedKafka.v1.Data

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

GcpConfig

Configuration properties for a Kafka cluster deployed to Google Cloud Platform.

HttpBody

Message that represents an arbitrary HTTP body. It should only be used for payload formats that can't be represented as JSON, such as raw binary or an HTML page. This message can be used both in streaming and non-streaming API methods in the request as well as the response. It can be used as a top-level request field, which is convenient if one wants to extract parameters from either the URL or HTTP template into the request fields and also want access to the raw HTTP body. Example: message GetResourceRequest { // A unique request id. string request_id = 1; // The raw HTTP body is bound to this field. google.api.HttpBody http_body = 2; } service ResourceService { rpc GetResource(GetResourceRequest) returns (google.api.HttpBody); rpc UpdateResource(google.api.HttpBody) returns (google.protobuf.Empty); } Example with streaming methods: service CaldavService { rpc GetCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); rpc UpdateCalendar(stream google.api.HttpBody) returns (stream google.api.HttpBody); } Use of this type only changes how the request and response bodies are handled, all other features will continue to work unchanged.

ListAclsResponse

Response for ListAcls.

ListClustersResponse

Response for ListClusters.

ListConnectClustersResponse

Response for ListConnectClusters.

ListConnectorsResponse

Response for ListConnectors.

ListConsumerGroupsResponse

Response for ListConsumerGroups.

ListLocationsResponse

The response message for Locations.ListLocations.

ListOperationsResponse

The response message for Operations.ListOperations.

ListSchemaRegistriesResponse

Request for ListSchemaRegistries.

ListTopicsResponse

Response for ListTopics.

Location

A resource that represents a Google Cloud location.

LookupVersionRequest

Request for LookupVersion.

NetworkConfig

The configuration of a Virtual Private Cloud (VPC) network that can access the Kafka cluster.

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.

PauseConnectorRequest

Request for PauseConnector.

PauseConnectorResponse

Response for PauseConnector.

RebalanceConfig

Defines rebalancing behavior of a Kafka cluster.

RemoveAclEntryResponse

Response for RemoveAclEntry.

RestartConnectorRequest

Request for RestartConnector.

RestartConnectorResponse

Response for RestartConnector.

ResumeConnectorRequest

Request for ResumeConnector.

ResumeConnectorResponse

Response for ResumeConnector.

Schema

Schema for a Kafka message.

SchemaConfig

SchemaConfig represents configuration for a schema registry or a specific subject.

SchemaMode

SchemaMode represents the mode of a schema registry or a specific subject. Four modes are supported: * NONE: This is the default mode for a subject and essentially means that the subject does not have any mode set. This means the subject will follow the schema registry's mode. * READONLY: The schema registry is in read-only mode.

READWRITE: The schema registry is in read-write mode, which allows limited write operations on the schema. * IMPORT: The schema registry is in import mode, which allows more editing operations on the schema for data importing purposes.

SchemaReference

SchemaReference is a reference to a schema.

SchemaRegistry

SchemaRegistry is a schema registry instance.

SchemaVersion

Version of a schema.

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.

StopConnectorRequest

Request for StopConnector.

StopConnectorResponse

Response for StopConnector.

TaskRetryPolicy

Task Retry Policy is implemented on a best-effort basis. Retry delay will be exponential based on provided minimum and maximum backoffs. https://en.wikipedia.org/wiki/Exponential_backoff. Note that the delay between consecutive task restarts may not always precisely match the configured settings. This can happen when the ConnectCluster is in rebalancing state or if the ConnectCluster is unresponsive etc. The default values for minimum and maximum backoffs are 60 seconds and 30 minutes respectively.