mirror of
https://github.com/status-im/consul.git
synced 2025-02-19 17:14:37 +00:00
51dcd126b7
* Add build system support for protobuf generation This is done generically so that we don’t have to keep updating the makefile to add another proto generation. Note: anything not in the vendor directory and with a .proto extension will be run through protoc if the corresponding namespace.pb.go file is not up to date. If you want to rebuild just a single proto file you can do so with: make proto-rebuild PROTOFILES=<list of proto files to rebuild> Providing the PROTOFILES var will override the default behavior of finding all the .proto files. * Start adding types to the agent/proto package These will be needed for some other work and are by no means comprehensive. * Add ability to resolve/fixup the agentpb.ACLLinks structure in the state store. * Use protobuf marshalling of raft requests instead of msgpack for protoc generated types. This does not change any encoding of existing types. * Removed structs package automatically encoding with protobuf marshalling Instead the caller of raftApply that wants to opt-in to protobuf encoding will have to call `raftApplyProtobuf` * Run update-vendor to fixup modules.txt Nothing changed as far as dependencies go but the ordering of modules in that file depends on the time they are first seen and its not alphabetical. * Rename some things and implement the structs.RPCInfo interface bits agentpb.QueryOptions and agentpb.WriteRequest implement 3 of the 4 RPCInfo funcs and the new TargetDatacenter message type implements the fourth. * Use the right encoding function. * Renamed agent/proto package to agent/agentpb to prevent package name conflicts * Update modules.txt to fix ordering * Change blockingQuery to take in interfaces for the query options and meta * Add %T to error output. * Add/Update some comments
83 lines
2.1 KiB
Protocol Buffer
83 lines
2.1 KiB
Protocol Buffer
/* This proto file contains the service and structures for implementing
|
|
* a Consul CA provider plugin. For clearer documentation on what each
|
|
* RPC method should do, please refer to the Go interface documentation
|
|
* for `agent/connect/ca.Provider`.
|
|
*
|
|
* After implementing this service, the plugin must also output the proper
|
|
* format to stdout for the plugin handshake. Please refer to the Consul
|
|
* documentation for more information.
|
|
*/
|
|
|
|
syntax = "proto3";
|
|
|
|
package plugin;
|
|
|
|
service CA {
|
|
rpc Configure(ConfigureRequest) returns (Empty);
|
|
rpc GenerateRoot(Empty) returns (Empty);
|
|
rpc ActiveRoot(Empty) returns (ActiveRootResponse);
|
|
rpc GenerateIntermediateCSR(Empty) returns (GenerateIntermediateCSRResponse);
|
|
rpc SetIntermediate(SetIntermediateRequest) returns (Empty);
|
|
rpc ActiveIntermediate(Empty) returns (ActiveIntermediateResponse);
|
|
rpc GenerateIntermediate(Empty) returns (GenerateIntermediateResponse);
|
|
rpc Sign(SignRequest) returns (SignResponse);
|
|
rpc SignIntermediate(SignIntermediateRequest) returns (SignIntermediateResponse);
|
|
rpc CrossSignCA(CrossSignCARequest) returns (CrossSignCAResponse);
|
|
rpc Cleanup(Empty) returns (Empty);
|
|
}
|
|
|
|
message ConfigureRequest {
|
|
string cluster_id = 1;
|
|
bool is_root = 2;
|
|
bytes config = 3; // JSON-encoded structure
|
|
}
|
|
|
|
message SetIntermediateRequest {
|
|
string intermediate_pem = 1;
|
|
string root_pem = 2;
|
|
}
|
|
|
|
message SignRequest {
|
|
bytes csr = 1;
|
|
}
|
|
|
|
message SignIntermediateRequest {
|
|
bytes csr = 1;
|
|
}
|
|
|
|
message CrossSignCARequest {
|
|
bytes crt = 1;
|
|
}
|
|
|
|
message ActiveRootResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
message GenerateIntermediateCSRResponse {
|
|
string csr_pem = 1;
|
|
}
|
|
|
|
message ActiveIntermediateResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
message GenerateIntermediateResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
message SignResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
message SignIntermediateResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
message CrossSignCAResponse {
|
|
string crt_pem = 1;
|
|
}
|
|
|
|
// Protobufs doesn't allow no req/resp so in the cases where there are
|
|
// no arguments we use the Empty message.
|
|
message Empty {}
|