May I make a proposal : adding `remote` flag also? 🙂 #Concern : It seems like we are sort of allowing users to assume what the ones without `local` flag are (are called by the community).
#Possible Benfit : Users will benefit from not having to think about what ` non-local` clusters are called. # Use-case : when someone automates counting how many remotes and clusters are there in list via shell-script, or simple String parser where the user will benefit more when grouping by `local` vs `remote`, rather than `local` vs `“”`. # Original Github Comment : https://github.com/apache/pulsar/pull/20614#issuecomment-1599025705 On 2023/06/20 06:00:29 guo jiwei wrote: > Hi community: > After configuring the geo-replication on Pulsar clusters, the `clusters > list` API will return multiple clusters, including the local Pulsar cluster > and remote clusters like > > ``` > bin/pulsar-admin clusters list > us-west > us-east > us-cent > ``` > But in this return, you can't distinguish the local and the remote cluster. > When you need to remove the geo-replication configuration, it will be hard > to decide which cluster should be removed on replicated tenants and > namespaces unless you record the cluster information. > > > ### Modification > Add `local` flag to distinguish clusters > ``` > bin/pulsar-admin clusters list > us-west(local) > us-east > us-cent > ``` > > PIP: https://github.com/apache/pulsar/pull/20614 > > > Regards > Jiwei Guo (Tboy) >
