363d692f35
After several requests for information about platform support, configuration introspection and feature switches, we now have a solution that should work in all these use cases. The Introspection API hooks into the plugin subsystem registration process. During registration, plugins declare several pieces of information, allowing clients to discover the cababilities and support that a containerd instance provides, including whether or not it loaded with an error. To allow symmetrical error reporting, the `google/rpc.Status` protobuf definitions have been brought in from the googleapis project. Unfortunately, we had to generate these in place to match our protobuf system. Once we like this design, we can add an implementation to integrate it directly with the plugin system. Enjoy! Signed-off-by: Stephen J Day <stephen.day@docker.com> |
||
|---|---|---|
| .. | ||
| code.pb.go | ||
| code.proto | ||
| doc.go | ||
| error_details.pb.go | ||
| error_details.proto | ||
| README.md | ||
| status.pb.go | ||
| status.proto | ||
This package copies definitions used with GRPC to represent error conditions within GRPC data types. These files are licensed under the provisions outlined at the top of each file.
containerd
This is moved from the googleapis project to allow us to regenerate these types for use with gogoprotobuf. We can move this away if google can generate these sensibly.
These files were imported from changes after 7f47d894837ac1701ee555fd5c3d70e5d4a796b1. Updates should not be required.
The other option is to get these into an upstream project, like gogoprotobuf.
Note that the go_package option has been changed so that they generate
correctly in a common package in the containerd project.