0910c41d95
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> |
||
|---|---|---|
| .. | ||
| health_snapshot.go | ||
| health_snapshot_test.go | ||
| replication.go | ||
| service.go | ||
| service_oss_test.go | ||
| service_test.go | ||
| stream_test.go | ||
| stream_tracker.go | ||
| stream_tracker_test.go | ||
| subscription_blocking.go | ||
| subscription_manager.go | ||
| subscription_manager_test.go | ||
| subscription_state.go | ||
| subscription_state_test.go | ||
| subscription_view.go | ||
| subscription_view_test.go | ||
| testing.go | ||
| testutil_oss_test.go | ||
| validate.go | ||
| validate_test.go | ||