Re: [Architecture] CLI Client for the Message Broker

[Eranda Rajapakshe]

Hi all,

When writing the HTTP client in CLI, I have used Java HttpUrlConnection
without going for a 3rd party libraries to maintain the size minimum as
possible.

But the REST API of the Broker admin service (which CLI client connects) is
designed using a swagger file. So instead of writing a separate HTTP client
inside the CLI, we can point it to the swagger file in the REST service and
generate a Swagger Java client and use it. With this approach, we don't
need to implement any HTTP related code, but it will only be a method call
which maps to the REST service. Even if any change happen on the side of
the REST service those will get integrated into the CLI HTTP client
seamlessly.

The only disadvantage of this swagger based approach is that it will come
with few external libraries. So those jars have to be packed into the
message-broker distribution.  Following are the extra jars needs to be
packaged,

*upgrade *gson version to 2.8.1 (+42kB)
joda-time 2.9.9 (634kB)
logging-interceptor 2.7.5 (8kB)
okhttp 2.7.5 (330kB)
okio 1.6.0 (65kB)

Also, we can implement the HTTP client using netty (netty is already
packaged in the broker distribution) as well, but since CLI client will run
on a single thread may be the overhead of using netty can be too much.
Also, we can go with libraries which has simpler abstractions as well,
HttpClient (748KB) [1] okHttp (396KB) [2].

Please let me know any thoughts on this.

[1]. https://hc.apache.org/httpcomponents-client-ga/
[2]. http://square.github.io/okhttp/

Thanks,

On Wed, Feb 21, 2018 at 5:08 PM, Eranda Rajapakshe  wrote:

> Hi Charitha,
>
> You will be able to find it in /bin directory under the name "
> broker-admin.sh".  In that release, it supports only exchanges related
> operations.
>
> Thanks,
>
> On Wed, Feb 21, 2018 at 3:25 PM, Charitha Goonetilleke  > wrote:
>
>> Hi Eranda,
>>
>> I have downloaded the release from above link and tried to experience the
>> CLI client. But I wasn't able to find the separate script which can used to
>> start the client. Could you please provide me some guidance?
>>
>> Thanks & Regards,
>> /charithag
>>
>> On Fri, Feb 16, 2018 at 9:09 AM, Eranda Rajapakshe 
>> wrote:
>>
>>> Hi Chamila, Kavindu,
>>>
>>> Yes, we are going ahead with design 2 approach. For the moment we are
>>> including the CLI Client inside the Broker pack itself and it will start
>>> with a separate script. Also since we are packaging it inside Broker zip,
>>> we have changed the implementation language to java as it will be more
>>> smooth and we can also re-use some libraries.
>>>
>>> We have packaged an initial version of the CLI client in the latest
>>> weekly release [1]
>>>
>>> [1]. https://github.com/wso2/message-broker/releases/tag/v4.0.47
>>>
>>> Thanks,
>>>
>>> On Thu, Feb 15, 2018 at 11:04 AM, Kavindu Zoysa 
>>> wrote:
>>>
 Hi Eranda,

>
> Furthermore, when implementing helper commands like `help` and
> `version`, it might be better to duplicate WUM client designs as we need 
> to
> provide a single experience for all WSO2 clients. WDYT?
>

 As Chamila mentioned it is better to duplicate WUM client designs and
 implementations(both UX designs and code level implementation), because
 people are using WUM for a reasonable time and, UX designs and
 implementations are stable. There fore it is better to duplicate it.

 Thank you,
 Kavindu



 ___
 Architecture mailing list
 Architecture@wso2.org
 https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture


>>>
>>>
>>> --
>>> *Eranda Rajapakshe*
>>> Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94784822608
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Charitha Goonetilleke*
>> Senior Software Engineer
>> WSO2 Inc.; http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 77 751 3669 <%2B94777513669>
>> Twitter:@CharithaWs , fb: charithag
>> , linkedin: charithag
>> 
>>
>> 
>>
>
>
>
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>



-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Eranda Rajapakshe]

Hi Charitha,

You will be able to find it in /bin directory under the name "
broker-admin.sh".  In that release, it supports only exchanges related
operations.

Thanks,

On Wed, Feb 21, 2018 at 3:25 PM, Charitha Goonetilleke 
wrote:

> Hi Eranda,
>
> I have downloaded the release from above link and tried to experience the
> CLI client. But I wasn't able to find the separate script which can used to
> start the client. Could you please provide me some guidance?
>
> Thanks & Regards,
> /charithag
>
> On Fri, Feb 16, 2018 at 9:09 AM, Eranda Rajapakshe 
> wrote:
>
>> Hi Chamila, Kavindu,
>>
>> Yes, we are going ahead with design 2 approach. For the moment we are
>> including the CLI Client inside the Broker pack itself and it will start
>> with a separate script. Also since we are packaging it inside Broker zip,
>> we have changed the implementation language to java as it will be more
>> smooth and we can also re-use some libraries.
>>
>> We have packaged an initial version of the CLI client in the latest
>> weekly release [1]
>>
>> [1]. https://github.com/wso2/message-broker/releases/tag/v4.0.47
>>
>> Thanks,
>>
>> On Thu, Feb 15, 2018 at 11:04 AM, Kavindu Zoysa  wrote:
>>
>>> Hi Eranda,
>>>

 Furthermore, when implementing helper commands like `help` and
 `version`, it might be better to duplicate WUM client designs as we need to
 provide a single experience for all WSO2 clients. WDYT?

>>>
>>> As Chamila mentioned it is better to duplicate WUM client designs and
>>> implementations(both UX designs and code level implementation), because
>>> people are using WUM for a reasonable time and, UX designs and
>>> implementations are stable. There fore it is better to duplicate it.
>>>
>>> Thank you,
>>> Kavindu
>>>
>>>
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Eranda Rajapakshe*
>> Software Engineer
>> WSO2 Inc.
>> Mobile : +94784822608
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Charitha Goonetilleke*
> Senior Software Engineer
> WSO2 Inc.; http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 77 751 3669 <%2B94777513669>
> Twitter:@CharithaWs , fb: charithag
> , linkedin: charithag
> 
>
> 
>



-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Charitha Goonetilleke]

Hi Eranda,

I have downloaded the release from above link and tried to experience the
CLI client. But I wasn't able to find the separate script which can used to
start the client. Could you please provide me some guidance?

Thanks & Regards,
/charithag

On Fri, Feb 16, 2018 at 9:09 AM, Eranda Rajapakshe  wrote:

> Hi Chamila, Kavindu,
>
> Yes, we are going ahead with design 2 approach. For the moment we are
> including the CLI Client inside the Broker pack itself and it will start
> with a separate script. Also since we are packaging it inside Broker zip,
> we have changed the implementation language to java as it will be more
> smooth and we can also re-use some libraries.
>
> We have packaged an initial version of the CLI client in the latest weekly
> release [1]
>
> [1]. https://github.com/wso2/message-broker/releases/tag/v4.0.47
>
> Thanks,
>
> On Thu, Feb 15, 2018 at 11:04 AM, Kavindu Zoysa  wrote:
>
>> Hi Eranda,
>>
>>>
>>> Furthermore, when implementing helper commands like `help` and
>>> `version`, it might be better to duplicate WUM client designs as we need to
>>> provide a single experience for all WSO2 clients. WDYT?
>>>
>>
>> As Chamila mentioned it is better to duplicate WUM client designs and
>> implementations(both UX designs and code level implementation), because
>> people are using WUM for a reasonable time and, UX designs and
>> implementations are stable. There fore it is better to duplicate it.
>>
>> Thank you,
>> Kavindu
>>
>>
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Charitha Goonetilleke*
Senior Software Engineer
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware

mobile: +94 77 751 3669 <%2B94777513669>
Twitter:@CharithaWs , fb: charithag
, linkedin: charithag



___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Eranda Rajapakshe]

Hi Chamila, Kavindu,

Yes, we are going ahead with design 2 approach. For the moment we are
including the CLI Client inside the Broker pack itself and it will start
with a separate script. Also since we are packaging it inside Broker zip,
we have changed the implementation language to java as it will be more
smooth and we can also re-use some libraries.

We have packaged an initial version of the CLI client in the latest weekly
release [1]

[1]. https://github.com/wso2/message-broker/releases/tag/v4.0.47

Thanks,

On Thu, Feb 15, 2018 at 11:04 AM, Kavindu Zoysa  wrote:

> Hi Eranda,
>
>>
>> Furthermore, when implementing helper commands like `help` and `version`,
>> it might be better to duplicate WUM client designs as we need to provide a
>> single experience for all WSO2 clients. WDYT?
>>
>
> As Chamila mentioned it is better to duplicate WUM client designs and
> implementations(both UX designs and code level implementation), because
> people are using WUM for a reasonable time and, UX designs and
> implementations are stable. There fore it is better to duplicate it.
>
> Thank you,
> Kavindu
>
>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Kavindu Zoysa]

Hi Eranda,

>
> Furthermore, when implementing helper commands like `help` and `version`,
> it might be better to duplicate WUM client designs as we need to provide a
> single experience for all WSO2 clients. WDYT?
>

As Chamila mentioned it is better to duplicate WUM client designs and
implementations(both UX designs and code level implementation), because
people are using WUM for a reasonable time and, UX designs and
implementations are stable. There fore it is better to duplicate it.

Thank you,
Kavindu
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Chamila De Alwis]

Hi Eranda,

Design-wise I'm more in favor of Design 2 where commands feel more natural
(` list exchange` as opposed to ` exchange list`). This would be
a bit more complex to implement in terms of code, but IMO UX is better with
design 2. This aligns to both WUM approach (which is a pattern most users
expect from WSO2) and the widespread `kubectl` approach (It should be noted
that AWS CLI implements commands similar to design 1).

Furthermore, when implementing helper commands like `help` and `version`,
it might be better to duplicate WUM client designs as we need to provide a
single experience for all WSO2 clients. WDYT?

+1 for Go implementation. How are we planning to ship the CLI? Is it going
to be a separate download? (if so, how would we ship updates for it?) From
maintenance point of view, offloading most business logic to the REST API
would be the better choice as a single version fo the CLI would be able to
work with a range of server versions.


Regards,
Chamila de Alwis
Committer and PMC Member - Apache Stratos
Associate Technical Lead | WSO2
+94 77 220 7163
Blog: https://medium.com/@chamilad



On Wed, Feb 7, 2018 at 3:51 PM, Dakshika Jayathilaka 
wrote:

> Hi All,
>
> IMO we need to support basic level features such as *--help*, *--version*
> and *--verbose* on each CLI tool that we are building.
>
> Also, we need to think about the standard output for each scenario as
> well. Shall we add few samples for that as well?
>
> Regards,
>
> *Dakshika Jayathilaka*
> PMC Member & Committer of Apache Stratos
> Associate Technical Lead
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
> On Wed, Feb 7, 2018 at 10:24 AM, Eranda Rajapakshe 
> wrote:
>
>> Hi Imesh,
>>
>> Yes, we are going to include help command into the client. Thanks for the
>> reference, it looks interesting.
>>
>> Thanks,
>>
>> On Wed, Feb 7, 2018 at 10:13 AM, Imesh Chandrasiri 
>> wrote:
>>
>>> Hi Eranda,
>>>
>>> A small clarification on the commands. Could these have a '--help'
>>> command where the syntax and the usage of the command is printed? IMHO it
>>> would benefit the user to figure out the command usage then and there
>>> without having to read the documentation. This is a nice article[1
>>> ] on some UX views of a CLI.
>>>
>>> [1] - https://zapier.com/engineering/how-to-cli/
>>>
>>> ___
>>> Architecture mailing list
>>> Architecture@wso2.org
>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>>
>>>
>>
>>
>> --
>> *Eranda Rajapakshe*
>> Software Engineer
>> WSO2 Inc.
>> Mobile : +94784822608
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Dakshika Jayathilaka]

Hi All,

IMO we need to support basic level features such as *--help*, *--version*
and *--verbose* on each CLI tool that we are building.

Also, we need to think about the standard output for each scenario as well.
Shall we add few samples for that as well?

Regards,

*Dakshika Jayathilaka*
PMC Member & Committer of Apache Stratos
Associate Technical Lead
WSO2, Inc.
lean.enterprise.middleware
0771100911

On Wed, Feb 7, 2018 at 10:24 AM, Eranda Rajapakshe  wrote:

> Hi Imesh,
>
> Yes, we are going to include help command into the client. Thanks for the
> reference, it looks interesting.
>
> Thanks,
>
> On Wed, Feb 7, 2018 at 10:13 AM, Imesh Chandrasiri 
> wrote:
>
>> Hi Eranda,
>>
>> A small clarification on the commands. Could these have a '--help'
>> command where the syntax and the usage of the command is printed? IMHO it
>> would benefit the user to figure out the command usage then and there
>> without having to read the documentation. This is a nice article[1
>> ] on some UX views of a CLI.
>>
>> [1] - https://zapier.com/engineering/how-to-cli/
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Eranda Rajapakshe]

Hi Imesh,

Yes, we are going to include help command into the client. Thanks for the
reference, it looks interesting.

Thanks,

On Wed, Feb 7, 2018 at 10:13 AM, Imesh Chandrasiri  wrote:

> Hi Eranda,
>
> A small clarification on the commands. Could these have a '--help' command
> where the syntax and the usage of the command is printed? IMHO it would
> benefit the user to figure out the command usage then and there without
> having to read the documentation. This is a nice article[1
> ] on some UX views of a CLI.
>
> [1] - https://zapier.com/engineering/how-to-cli/
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Imesh Chandrasiri]

Hi Eranda,

A small clarification on the commands. Could these have a '--help' command
where the syntax and the usage of the command is printed? IMHO it would
benefit the user to figure out the command usage then and there without
having to read the documentation. This is a nice article[1
] on some UX views of a CLI.

[1] - https://zapier.com/engineering/how-to-cli/
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Eranda Rajapakshe]

Hi Milinda, Asanka,

On Tue, Feb 6, 2018 at 10:08 PM, Milinda Perera  wrote:

> Hi Eranda,
>
> Do we have plans to add tab completion[1] for this CLI client?
> I believe it will improvement for UX. And users (especially devOps) will
> appreciate that.
>

Thanks Milinda. Yes thats something we can include I believe.

>
> [1] https://en.wikipedia.org/wiki/Command-line_completion
>
> Thanks,
> Milinda
>
> On Tue, Feb 6, 2018 at 9:45 PM, Asanka Abeyweera 
> wrote:
>
>> Hi Eranda,
>>
>>1. Aren't we going to handle granting permission as well?
>>
>> Yes we have to handle that use-cases as well. Since core features to that
are realted to authorization features are still under developement, I
didn't include them in them in the design yet.

>
>>1. Can we handle a scenario like removing all consumers for a queue
>>using a single command?  I was just thinking if we can chain different
>>commands together to achieve complex scenarios.
>>
>> Yes its possible to do such a thing, I and feel that its a good feature
to have. With this CLI client Im invoking the REST admin service of the
Broker. So instead of implementing the chain of commands in the client side
we can consider implemeting that on the Brokers REST service, which will
reduce the network overhead. +1 for the scenario

>
>>
>> On Tue, Feb 6, 2018 at 7:20 PM, Eranda Rajapakshe 
>> wrote:
>>
>>> Hi all,
>>>
>>> I am working on designing a CLI client for the MB4. Purpose of this is
>>> to provide administrative features to the user through a command line
>>> interface. CLI client will use the REST API interface of the Broker to
>>> interact.
>>>
>>> Administrative tasks including following will be able to perform through
>>> the proposed CLI,
>>> * Authenticate users
>>> * Create queue, exchanges and bindings
>>> * View queue info, exchange info, bindings info and consumer info
>>> * Delete queues, exchanges, bindings and consumers
>>>
>>> I have done a draft syntax design for the CLI commands [1
>>> ]
>>> Please go through it and suggest any improvements. There are two designs in
>>> the document, one is going with the flow of REST API of the MB and the
>>> other will have a more generic approach.
>>>
>>> Also when implementing I don't think we need to stick strictly
>>> into Java, as this is a separate program which can even be run on a
>>> different machine. So we can even consider a GoLang based CLI client.
>>>
>>> [1]. https://docs.google.com/document/d/1z1FSpotL1SdGzM7ee-d
>>> CEdCYhQLhLnyr_IixvTAVrkk/edit#heading=h.o94yuusu8o9t
>>>
>>> Thanks,
>>> --
>>> *Eranda Rajapakshe*
>>> Software Engineer
>>> WSO2 Inc.
>>> Mobile : +94784822608
>>>
>>
>>
>>
>> --
>> Asanka Abeyweera
>> Associate Technical Lead
>> WSO2 Inc.
>>
>> Phone: +94 712228648 <+94%2071%20222%208648>
>> Blog: a5anka.github.io
>>
>> 
>>
>> ___
>> Architecture mailing list
>> Architecture@wso2.org
>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>>
>>
>
>
> --
> Milinda Perera
> Senior Software Engineer;
> WSO2 Inc. http://wso2.com ,
> Mobile: (+94) 714 115 032 <+94%2071%20411%205032>
>
>


-- 
*Eranda Rajapakshe*
Software Engineer
WSO2 Inc.
Mobile : +94784822608
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Milinda Perera]

Hi Eranda,

Do we have plans to add tab completion[1] for this CLI client?
I believe it will improvement for UX. And users (especially devOps) will
appreciate that.

[1] https://en.wikipedia.org/wiki/Command-line_completion

Thanks,
Milinda

On Tue, Feb 6, 2018 at 9:45 PM, Asanka Abeyweera  wrote:

> Hi Eranda,
>
>1. Aren't we going to handle granting permission as well?
>2. Can we handle a scenario like removing all consumers for a queue
>using a single command?  I was just thinking if we can chain different
>commands together to achieve complex scenarios.
>
>
>
>
> On Tue, Feb 6, 2018 at 7:20 PM, Eranda Rajapakshe 
> wrote:
>
>> Hi all,
>>
>> I am working on designing a CLI client for the MB4. Purpose of this is to
>> provide administrative features to the user through a command line
>> interface. CLI client will use the REST API interface of the Broker to
>> interact.
>>
>> Administrative tasks including following will be able to perform through
>> the proposed CLI,
>> * Authenticate users
>> * Create queue, exchanges and bindings
>> * View queue info, exchange info, bindings info and consumer info
>> * Delete queues, exchanges, bindings and consumers
>>
>> I have done a draft syntax design for the CLI commands [1
>> ]
>> Please go through it and suggest any improvements. There are two designs in
>> the document, one is going with the flow of REST API of the MB and the
>> other will have a more generic approach.
>>
>> Also when implementing I don't think we need to stick strictly into Java,
>> as this is a separate program which can even be run on a different machine.
>> So we can even consider a GoLang based CLI client.
>>
>> [1]. https://docs.google.com/document/d/1z1FSpotL1SdGzM7ee-d
>> CEdCYhQLhLnyr_IixvTAVrkk/edit#heading=h.o94yuusu8o9t
>>
>> Thanks,
>> --
>> *Eranda Rajapakshe*
>> Software Engineer
>> WSO2 Inc.
>> Mobile : +94784822608
>>
>
>
>
> --
> Asanka Abeyweera
> Associate Technical Lead
> WSO2 Inc.
>
> Phone: +94 712228648 <+94%2071%20222%208648>
> Blog: a5anka.github.io
>
> 
>
> ___
> Architecture mailing list
> Architecture@wso2.org
> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
>
>


-- 
Milinda Perera
Senior Software Engineer;
WSO2 Inc. http://wso2.com ,
Mobile: (+94) 714 115 032
___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Re: [Architecture] CLI Client for the Message Broker

[Asanka Abeyweera]

Hi Eranda,

   1. Aren't we going to handle granting permission as well?
   2. Can we handle a scenario like removing all consumers for a queue
   using a single command?  I was just thinking if we can chain different
   commands together to achieve complex scenarios.




On Tue, Feb 6, 2018 at 7:20 PM, Eranda Rajapakshe  wrote:

> Hi all,
>
> I am working on designing a CLI client for the MB4. Purpose of this is to
> provide administrative features to the user through a command line
> interface. CLI client will use the REST API interface of the Broker to
> interact.
>
> Administrative tasks including following will be able to perform through
> the proposed CLI,
> * Authenticate users
> * Create queue, exchanges and bindings
> * View queue info, exchange info, bindings info and consumer info
> * Delete queues, exchanges, bindings and consumers
>
> I have done a draft syntax design for the CLI commands [1
> ]
> Please go through it and suggest any improvements. There are two designs in
> the document, one is going with the flow of REST API of the MB and the
> other will have a more generic approach.
>
> Also when implementing I don't think we need to stick strictly into Java,
> as this is a separate program which can even be run on a different machine.
> So we can even consider a GoLang based CLI client.
>
> [1]. https://docs.google.com/document/d/1z1FSpotL1SdGzM7ee-
> dCEdCYhQLhLnyr_IixvTAVrkk/edit#heading=h.o94yuusu8o9t
>
> Thanks,
> --
> *Eranda Rajapakshe*
> Software Engineer
> WSO2 Inc.
> Mobile : +94784822608
>



-- 
Asanka Abeyweera
Associate Technical Lead
WSO2 Inc.

Phone: +94 712228648
Blog: a5anka.github.io


___
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture