open-consul/proto/pbpeering
R.B. Boyer dae47101fa
api: ensure peering API endpoints do not use protobufs (#13204)
I noticed that the JSON api endpoints for peerings json encodes protobufs directly, rather than converting them into their `api` package equivalents before marshal/unmarshaling them.

I updated this and used `mog` to do the annoying part in the middle. 

Other changes:
- the status enum was converted into the friendlier string form of the enum for readability with tools like `curl`
- some of the `api` library functions were slightly modified to match other similar endpoints in UX (cc: @ndhanushkodi )
- peeringRead returns `nil` if not found
- partitions are NOT inferred from the agent's partition (matching 1.11-style logic)
2022-05-25 13:43:35 -05:00
..
generate.go peering: initial sync (#12842) 2022-04-21 17:34:40 -05:00
peering.gen.go api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
peering.go api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
peering.pb.binary.go peering: add TrustBundleListByService endpoint (#13048) 2022-05-12 15:58:22 -07:00
peering.pb.go api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
peering.proto api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
peering.rpcglue.pb.go peering: add TrustBundleListByService endpoint (#13048) 2022-05-12 15:58:22 -07:00
peering_grpc.pb.go Migrate from `protoc` to `buf` (#12841) 2022-05-23 10:37:52 -04:00
peering_oss.go peering: initial sync (#12842) 2022-04-21 17:34:40 -05:00
types.go peering: initial sync (#12842) 2022-04-21 17:34:40 -05:00