consul/proto
R.B. Boyer a85b8a4705
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
..
pbacl Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbautoconf Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbcommon Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbconfig Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbconnect Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbpeering api: ensure peering API endpoints do not use protobufs (#13204) 2022-05-25 13:43:35 -05:00
pbservice peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218) 2022-05-25 12:37:44 -05:00
pbstatus Specify go_package explicitly 2022-05-24 10:22:53 -07:00
pbsubscribe Specify go_package explicitly 2022-05-24 10:22:53 -07:00
prototest peering: replicate expected SNI, SPIFFE, and service protocol to peers (#13218) 2022-05-25 12:37:44 -05:00
buf.gen.yaml Migrate from `protoc` to `buf` (#12841) 2022-05-23 10:37:52 -04:00
buf.yaml Migrate from `protoc` to `buf` (#12841) 2022-05-23 10:37:52 -04:00