Denier
This adapter supports the checknothing template,the ,and the quota template.
Configuration format for the Denier adapter.
google.rpc.Status
The Status
type defines a logical error model that is suitable fordifferent programming environments, including REST APIs and RPC APIs. It isused by gRPC. The error model is designed to be:
- Simple to use and understand for most users
- Flexible enough to meet unexpected needs
The Status
message is the logical representation of the error model, but itis not necessarily the actual wire format. When the Status
message isexposed in different client libraries and different wire protocols, it can bemapped differently. For example, it will likely be mapped to some exceptionsin Java, but more likely mapped to some error codes in C.
The error model and the Status
message can be used in a variety ofenvironments, either with or without APIs, to provide aconsistent developer experience across different environments.
Example uses of this error model include:
Workflow errors. A typical workflow has multiple steps. Each step mayhave 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 foreach error sub-response.Asynchronous operations. If an API call embeds asynchronous operationresults in its response, the status of those operations should berepresented directly using the message.
Field | Type | Description | Required |
---|---|---|---|
code | int32 | The status code, which should be an enum value ofgoogle.rpc.Code. | No |
message | string | A developer-facing error message, which should be in English. Anyuser-facing error message should be localized and sent in the field, or localizedby the client. | No |
details | Any[] | A list of messages that carry the error details. There is a common set ofmessage types for APIs to use. | No |