Improving the Geo UI when object storage is configured with 3rd party replication or with the same buckets on primary and secondary

Problem to solve

We have 3 scenarios when it comes to object storage configuration with Geo:

1. We can have separate buckets and Geo handles replication.
2. We can have primary and secondary connected to the same buckets.
3. We can have separate buckets, but replication is handled by a third-party, not by Geo.

In scenarios 2 and 3, Geo UI looks rather confusing:

• For primary, it shows Verification information successfully.
• For secondary, it will show Nothing to synchronize and Nothing to verify. There might be an impression that something is wrong because of that.

Proposal

Instead of showing Nothing to synchronize and Nothing to verify for the secondaries we should show:

• For scenario 2 - something like Replication/verification is not happening because you are using the same buckets on your primary and secondary instances.
• For scenarios 3 - something like Replication is handled by a 3rd-party.