happygapi.cloudshell.operations — happygapi 0.4.5

Cloud Shell API: operations. Allows users to start, configure, and connect to interactive shell sessions running in the cloud. See: https://cloud.google.com/shell/docs/api/reference/rest/v1/operations

cancel$ clj

(cancel$ auth parameters body)

https://cloud.google.com/shell/docs/api/reference/rest/v1/operations/cancel

Required parameters: name

Optional parameters: none

Body:

{}

Starts asynchronous cancellation on a long-running operation. The server makes a best effort to cancel the operation, but success is not guaranteed. If the server doesn't support this method, it returns google.rpc.Code.UNIMPLEMENTED. Clients can use Operations.GetOperation or other methods to check whether the cancellation succeeded or whether the operation completed despite cancellation. On successful cancellation, the operation is not deleted; instead, it becomes an operation with an Operation.error value with a google.rpc.Status.code of 1, corresponding to Code.CANCELLED.

delete$ clj

(delete$ auth parameters)

https://cloud.google.com/shell/docs/api/reference/rest/v1/operations/delete

Required parameters: name

Optional parameters: none

Deletes a long-running operation. This method indicates that the client is no longer interested in the operation result. It does not cancel the operation. If the server doesn't support this method, it returns google.rpc.Code.UNIMPLEMENTED.

get$ clj

(get$ auth parameters)

https://cloud.google.com/shell/docs/api/reference/rest/v1/operations/get

Required parameters: name

Optional parameters: none

Gets the latest state of a long-running operation. Clients can use this method to poll the operation result at intervals as recommended by the API service.

list$ clj

(list$ auth parameters)

https://cloud.google.com/shell/docs/api/reference/rest/v1/operations/list

Required parameters: name

Optional parameters: filter, pageSize, pageToken

Lists operations that match the specified filter in the request. If the server doesn't support this method, it returns UNIMPLEMENTED. NOTE: the name binding allows API services to override the binding to use different resource name schemes, such as users/*/operations. To override the binding, API services can add a binding such as "/v1/{name=users/*}/operations" to their service configuration. For backwards compatibility, the default name includes the operations collection id, however overriding users must ensure the name binding is the parent resource, without the operations collection id.