Manage Apache Kafka clusters and resources.

The configuration of access to the Kafka cluster.

The request message for Operations.CancelOperation.

A capacity configuration of a Kafka cluster.

An Apache Kafka cluster deployed in a location.

The configuration of access to the Kafka Connect cluster.

An Apache Kafka Connect cluster deployed in a location.

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

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

A Kafka Connect connector in a given ConnectCluster.

A Kafka consumer group in a given cluster.

Metadata for a consumer group corresponding to a specific partition.

Metadata for a consumer group corresponding to a specific topic.

Defines the root interface for all clients that generate credentials for calling Google APIs. All clients should implement this interface.

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

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

Response for ListClusters.

Response for ListConnectClusters.

Response for ListConnectors.

Response for ListConsumerGroups.

The response message for Locations.ListLocations.

The response message for Operations.ListOperations.

Response for ListTopics.

A resource that represents a Google Cloud location.

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

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

Represents the metadata of the long-running operation.

Request for PauseConnector.

Response for PauseConnector.

Additional options for ManagedKafka#projectsLocationsClustersConsumerGroupsList.

Additional options for ManagedKafka#projectsLocationsClustersConsumerGroupsPatch.

Additional options for ManagedKafka#projectsLocationsClustersCreate.

Additional options for ManagedKafka#projectsLocationsClustersDelete.

Additional options for ManagedKafka#projectsLocationsClustersList.

Additional options for ManagedKafka#projectsLocationsClustersPatch.

Additional options for ManagedKafka#projectsLocationsClustersTopicsCreate.

Additional options for ManagedKafka#projectsLocationsClustersTopicsList.

Additional options for ManagedKafka#projectsLocationsClustersTopicsPatch.

Additional options for ManagedKafka#projectsLocationsConnectClustersConnectorsCreate.

Additional options for ManagedKafka#projectsLocationsConnectClustersConnectorsList.

Additional options for ManagedKafka#projectsLocationsConnectClustersConnectorsPatch.

Additional options for ManagedKafka#projectsLocationsConnectClustersCreate.

Additional options for ManagedKafka#projectsLocationsConnectClustersDelete.

Additional options for ManagedKafka#projectsLocationsConnectClustersList.

Additional options for ManagedKafka#projectsLocationsConnectClustersPatch.

Additional options for ManagedKafka#projectsLocationsList.

Additional options for ManagedKafka#projectsLocationsOperationsList.

Defines rebalancing behavior of a Kafka cluster.

Request for RestartConnector.

Response for RestartConnector.

Request for ResumeConnector.

Response for ResumeConnector.

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.

Request for StopConnector.

Response for StopConnector.

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.

A Kafka topic in a given cluster.