View Source API Reference google_api_cloud_shell v0.20.2

Modules

API client metadata for GoogleApi.CloudShell.V1.

API calls for all endpoints tagged Operations.

API calls for all endpoints tagged Users.

Handle Tesla connections for GoogleApi.CloudShell.V1.

Message included in the metadata field of operations returned from AddPublicKey.

Request message for AddPublicKey.

Response message for AddPublicKey.

Message included in the metadata field of operations returned from AuthorizeEnvironment.

Request message for AuthorizeEnvironment.

Response message for AuthorizeEnvironment.

The request message for Operations.CancelOperation.

Message included in the metadata field of operations returned from CreateEnvironment.

Message included in the metadata field of operations returned from DeleteEnvironment.

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

A Cloud Shell environment, which is defined as the combination of a Docker image specifying what is installed on the environment and a home directory containing the user's data that will remain across sessions. Each user has at least an environment with the ID "default".

The response message for Operations.ListOperations.

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

Message included in the metadata field of operations returned from RemovePublicKey.

Request message for RemovePublicKey.

Response message for RemovePublicKey.

Message included in the metadata field of operations returned from StartEnvironment.

Request message for StartEnvironment.

Message included in the response field of operations returned from StartEnvironment once the operation is complete.

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.