While migrating from using the orchestrator command line tool to orchestrator-client to ensure that all access is done via an https interface I notice some differences:

e.g.

$ sudo orchestrator -c topology | head -3
host-2.example.com:3306              [0s,ok,5.7.25-log,rw,ROW,>>,P-GTID]
+ host-1.example.com:3306            [0s,ok,5.7.25-log,ro,ROW,>>,GTID,P-GTID]
  + host-3.example.com:3306          [0s,ok,5.7.26-log,ro,nobinlog,GTID,P-GTID]

sudo required as my /etc/orchestrator.conf.json configuration is only readable by root.

If I want to do the same with orchestrator-client I first setup something in /etc/profile.d/orchestrator-client.sh which will configure an appropriate setting for ORCHESTRATOR_API.

However, now running this I use the same input and get:

$ orchestrator-client -c topology
instance|alias must be provided

This is not required using the orchestrator binary.

The current work-around is this:

$ orchestrator-client -c topology -i $(hostname) | head -2
host-2.example.com:3306 [1s,ok,5.7.25-log,rw,ROW,>>,P-GTID]
+ host-1.example.com:3306 [1s,ok,5.7.25-log,ro,ROW,>>,GTID,P-GTID]

Several orchestrator commands allow the use of an implicit -i xxxxx value and I'd like to do the same (for compatibility) in orchestrator-client.

What's the best way from your perspective to approach this? On a case by case basis where I notice this functionality is missing, or in a more general manner? I can take a look at providing a patch but wasn't sure your preferred approach and first wanted to report the issue.