API calls for all endpoints tagged Operations

API calls for all endpoints tagged Projects

Handle Tesla connections for GoogleApi.CloudFunctions.V1

Helper functions for deserializing responses into models

Request for the `CallFunction` method

Response of `CallFunction` method

Describes a Cloud Function that contains user computation executed in response to an event. It encapsulate function and triggers configurations

Describes EventTrigger, used to request events be sent from another service

Describes the policy in case of function's execution failure. If empty, then defaults to ignoring failures (i.e. not retrying them)

Request of `GenerateDownloadUrl` method

Response of `GenerateDownloadUrl` method

Request of `GenerateSourceUploadUrl` method

Response of `GenerateSourceUploadUrl` method

Describes HttpsTrigger, could be used to connect web hooks to function

Response for the `ListFunctions` method

The response message for Locations.ListLocations

The response message for Operations.ListOperations

A resource that represents Google Cloud Platform location

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

Metadata describing an Operation

Metadata describing an Operation

Describes the retry policy in case of function's execution failure. A function execution will be retried on any failure. A failed execution will be retried up to 7 days with an exponential backoff (capped at 10 seconds). Retried execution is charged as any other execution

Describes SourceRepository, used to represent parameters related to source repository where a function is hosted

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. The error model is designed to be: - Simple to use and understand for most users - Flexible enough to meet unexpected needs # Overview The `Status` message contains three pieces of data: error code, error message, and error details. The error code should be an enum value of google.rpc.Code, but it may accept additional error codes if needed. The error message should be a developer-facing English message that helps developers understand and resolve the error. If a localized user-facing error message is needed, put the localized message in the error details or localize it in the client. The optional error details may contain arbitrary information about the error. There is a predefined set of error detail types in the package `google.rpc` that can be used for common error conditions. # Language mapping The `Status` message is the logical representation of the error model, but it is not necessarily the actual wire format. When the `Status` message is exposed in different client libraries and different wire protocols, it can be mapped differently. For example, it will likely be mapped to some exceptions in Java, but more likely mapped to some error codes in C. # Other uses The error model and the `Status` message can be used in a variety of environments, either with or without APIs, to provide a consistent developer experience across different environments. Example uses of this error model include: - Partial errors. If a service needs to return partial errors to the client, it may embed the `Status` in the normal response to indicate the partial errors. - Workflow errors. A typical workflow has multiple steps. Each step may have a `Status` message for error reporting. - Batch operations. If a client uses batch request and batch response, the `Status` message should be used directly inside batch response, one for each error sub-response. - Asynchronous operations. If an API call embeds asynchronous operation results in its response, the status of those operations should be represented directly using the `Status` message. - Logging. If some API errors are stored in logs, the message `Status` could be used directly after any stripping needed for security/privacy reasons

Helper functions for building Tesla requests