freddygv 6453375ab2 Add leader routine to clean up peerings ... Once a peering is marked for deletion a new leader routine will now clean up all imported resources and then the peering itself. A lot of the logic was grabbed from the namespace/partitions deferred deletions but with a handful of simplifications: - The rate limiting is not configurable. - Deleting imported nodes/services/checks is done by deleting nodes with the Txn API. The services and checks are deleted as a side-effect. - There is no "round rate limiter" like with namespaces and partitions. This is because peerings are purely local, and deleting a peering in the datacenter does not depend on deleting data from other DCs like with WAN-federated namespaces. All rate limiting is handled by the Raft rate limiter.		2022-06-14 15:36:50 -06:00
..
middleware	add more labels to RequestRecorder (#12727)	2022-04-12 10:50:25 -07:00
peering	Add leader routine to clean up peerings	2022-06-14 15:36:50 -06:00