Propagate RemoveRepository RPC to Praefect secondaries
There is a potential issue in how we handle removing a repo from Praefect. When Praefect receives a RemoveRepository
RPC, it will route to the primary and the repo will be removed. However, the secondaries should still contain a copy of that repository since the replication process is not destructive. Some possible solutions:
- When praefect encounters specific RPC's, a specific type of replication job will be dispatched (e.g. additive, destructive, etc.)
- The existing replication process could be modified to behave differently if the source location (primary) doesn't exist. In that case, the destination (secondaries) will be removed.