google_api_service_control v0.6.0 API Reference
Modules
API calls for all endpoints tagged Services
.
Handle Tesla connections for GoogleApi.ServiceControl.V1.
Helper functions for deserializing responses into models.
Attributes
- unusedArguments ([String.t]): A list of label keys that were unused by the server in processing the request. Thus, for similar requests repeated in a certain future time window, the caller can choose to ignore these labels in the requests to achieve better client-side cache hits and quota aggregation. Defaults to:
null
.
Request message for the AllocateQuota method.
Response message for the AllocateQuota method.
Common audit log format for Google Cloud Platform API operations.
This message defines request authentication attributes. Terminology is based on the JSON Web Token (JWT) standard, but the terms also correlate to concepts in other standards.
Authentication information for the operation.
Authorization information for the operation.
Defines the errors to be returned in google.api.servicecontrol.v1.CheckResponse.check_errors.
Contains additional information about the check operation.
Request message for the Check method.
Response message for the Check method.
`ConsumerInfo` provides information about the consumer.
Distribution represents a frequency distribution of double-valued sample points. It contains the size of the population of sample points plus additional optional information: - the arithmetic mean of the samples - the minimum and maximum of the samples - the sum-squared-deviation of the samples, used to compute variance - a histogram of the values of the sample points
Request message for QuotaController.EndReconciliation.
Response message for QuotaController.EndReconciliation.
Describing buckets with arbitrary user-provided width.
Describing buckets with exponentially growing width.
First party identity principal.
A common proto for logging HTTP requests. Only contains semantics defined by the HTTP specification. Product-specific logging information MUST be defined in a separate message.
Describing buckets with constant width.
An individual log entry.
Additional information about a potentially long-running operation with which a log entry is associated.
Represents a single metric value.
Represents a set of metric values in the same metric. Each metric value in the set should have a unique combination of start time, end time, and label values.
Represents an amount of money with its currency type.
Represents information regarding an operation.
This message defines attributes for a node that handles a network request. The node can be either a service or an application that sends, forwards, or receives the request. Service peers should fill in the `service`, `principal`, and `labels` as appropriate.
Represents error information for QuotaOperation.
Contains the quota information for a quota check response.
Represents information regarding a quota operation.
Represents the properties needed for quota operations.
Request message for the ReleaseQuota method.
Response message for the ReleaseQuota method.
Represents the processing error of one Operation in the request.
Contains additional info about the report operation.
Request message for the Report method.
Response message for the Report method.
This message defines attributes for an HTTP request. If the actual request is not an HTTP request, the runtime system should try to map the actual request to an equivalent HTTP request.
Metadata about the request.
This message defines core attributes for a resource. A resource is an addressable (named) entity provided by the destination service. For example, a file stored on a network storage service.
Describes a resource associated with this operation.
Location information about a resource.
Identity delegation history of an authenticated service account.
Request message for QuotaController.StartReconciliation.
Response message for QuotaController.StartReconciliation.
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.
Third party identity principal.
Helper functions for building Tesla requests.