consul/proto/pbpeering
Chris S. Kim f07132dacc
Revise possible states for a peering. (#13661)
These changes are primarily for Consul's UI, where we want to be more
specific about the state a peering is in.

- The "initial" state was renamed to pending, and no longer applies to
  peerings being established from a peering token.

- Upon request to establish a peering from a peering token, peerings
  will be set as "establishing". This will help distinguish between the
  two roles: the cluster that generates the peering token and the
  cluster that establishes the peering.

- When marked for deletion, peering state will be set to "deleting".
  This way the UI determines the deletion via the state rather than the
  "DeletedAt" field.

Co-authored-by: freddygv <freddy@hashicorp.com>
2022-07-04 10:47:58 -04:00
..
generate.go
peering.gen.go peering: add imported/exported counts to peering (#13644) 2022-06-29 14:07:30 -07:00
peering.go Revise possible states for a peering. (#13661) 2022-07-04 10:47:58 -04:00
peering.pb.binary.go peering: rename initiate to establish in the context of the APIs (#13419) 2022-06-10 11:10:46 -05:00
peering.pb.go Revise possible states for a peering. (#13661) 2022-07-04 10:47:58 -04:00
peering.proto Revise possible states for a peering. (#13661) 2022-07-04 10:47:58 -04:00
peering.rpcglue.pb.go peering: rename initiate to establish in the context of the APIs (#13419) 2022-06-10 11:10:46 -05:00
peering_grpc.pb.go peering: rename initiate to establish in the context of the APIs (#13419) 2022-06-10 11:10:46 -05:00
peering_oss.go
types.go Add support for streaming CA roots to peers (#13260) 2022-05-26 15:24:09 -04:00