googleapis/google/rpc
Google APIs f4b02617cb docs: Updated additional documentation link for field annotations in message .google.rpc.context.AttributeContext
docs: Clarified that field `metadata` in `google.rpc.ErrorInfo` should be lowerCamelCase
feat: Improved support for multiple `google.rpc.BadRequest.FieldViolation` errors

Added `reason` and `localized_messsage` fields to `google.rpc.BadRequest.FieldViolation`. This allows each violation to have a machine readable identifier and error message that is safe to return to the API consumer.

PiperOrigin-RevId: 707591563
2024-12-18 10:19:13 -08:00
..
context docs: Updated additional documentation link for field annotations in message .google.rpc.context.AttributeContext 2024-12-18 10:19:13 -08:00
BUILD.bazel chore(python): Add build rule for //google/rpc:rpc-py to prepare for release 2024-12-17 08:40:28 -08:00
code.proto chore: update copyright year for auto-generated protos 2024-05-07 13:56:05 -07:00
error_details.proto docs: Updated additional documentation link for field annotations in message .google.rpc.context.AttributeContext 2024-12-18 10:19:13 -08:00
http.proto chore: update copyright year for auto-generated protos 2024-05-07 13:56:05 -07:00
README.md chore: update README files 2023-10-11 10:16:35 -07:00
rpc_publish.yaml Synchronize new proto/yaml changes. 2019-11-01 13:39:38 -07:00
status.proto chore: update copyright year for auto-generated protos 2024-05-07 13:56:05 -07:00

RPC (Remote Procedure Call) Types

This package contains protocol buffer types that represent remote procedure call concepts. While gRPC uses these types, we encourage their use in any interested RPC implementation to promote compatibility and consistency.

Key Concepts

  • Code: An enum that represents an error code returned by an RPC. These error codes map to HTTP codes, but are slightly finer-grained. Every gRPC code has exactly one corresponding HTTP code; however, some HTTP codes have more than one corresponding gRPC code.
  • Error details: Any of the types contained in error_details.proto which provide extra details about particular types of failures.
  • Status: Combines a code, message, and error details to represent the success or failure details of an RPC call.