Personally, I see no reason for deprecating Visor CLI and moving all its capabilities to the control.sh script. It's better to merge the script's capabilities into Visor CLI and rework the connectivity/communication protocol of the latter. If to recall the reason for the control.sh creation it was the Visor's daemon-mode way of interaction with the cluster that is cumbersome and complicated.
- Denis On Thu, Dec 26, 2019 at 1:49 AM Ilya Kasnacheev <ilya.kasnach...@gmail.com> wrote: > Hello! > > I think that control.sh should be extended instead of Visor CLI, it is a > tool which sees a lot more activity currently. > > Regards, > -- > Ilya Kasnacheev > > > чт, 26 дек. 2019 г. в 12:45, Ivan Pavlukhin <vololo...@gmail.com>: > > > Folks, > > > > Do not we have plans to discontinue Visor? If so, it might be better > > to add a desired functionality to another management API? > > > > вт, 24 дек. 2019 г. в 08:02, Denis Magda <dma...@apache.org>: > > > > > > Forwarding to the dev list. How exactly would you like to expand Visor > > CMD? > > > Please describe your idea and we can mover from that point. > > > > > > Denis > > > > > > On Monday, December 23, 2019, sgtech19 <rajado...@gmail.com> wrote: > > > > > > > Hello team, > > > > I would like to add a new feature to the existing > > visor > > > > commands. Could you give me some direction on how to achieve this if > > its > > > > possible? Do we need a visor plugin ? if so,please provide any > example > > of > > > > this plugin . > > > > > > > > Thanks > > > > > > > > > > > > > > > > -- > > > > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ > > > > > > > > > > > > > -- > > > - > > > Denis > > > > > > > > -- > > Best regards, > > Ivan Pavlukhin > > >
