Hi Fathima, Few questions.
1. What will be the command template for general and app specifics? 2. Are you going to treat both the command categories via the same CommandFactory? Suggestion. If the user executes app specific commands inside the app repository we can detect the app name by scanning the git remotes, that way users won't have to explicitly define the appname in the command. However we shouldn't limit appspecific command to be executed only within the app repo, 'cause there might be cases where users might need to trigger builds/ download logs even without the repo (considering a large repo) WDYT? Regards, Anuruddha. On Thu, Jun 4, 2015 at 1:02 AM, Fathima Dilhasha <[email protected]> wrote: > Hi, > > In the spreadsheet at [1] > <https://docs.google.com/spreadsheets/d/1mq8wWlBjkDMmurfK7BZE3GvGlR2Fr8Gu7KcmahcKy2s/edit?usp=sharing>, > I have listed the requirements that need to be validated before each > command is executed. > Please update on any changes and corrections. > > [1] > https://docs.google.com/spreadsheets/d/1mq8wWlBjkDMmurfK7BZE3GvGlR2Fr8Gu7KcmahcKy2s/edit?usp=sharing > > Thanks. > Regards, > Dilhasha > > Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> > (M.N.F.Dilhasha) > Undergraduate | Department of Computer Science and Engineering > University of Moratuwa > Sri Lanka > > On Thu, Jun 4, 2015 at 1:10 PM, Fathima Dilhasha <[email protected]> > wrote: > >> Hi, >> >> I have come up with a design for rule based command execution in the CLI >> tool. Please find the attached class diagram. The basic idea is to have >> several implementations for the Command, so that all the available commands >> can be maintained in the command Factory. >> >> Your feedback and suggestions on this rule based approach are highly >> appreciated. >> >> Thanks. >> Regards, >> Dilhasha >> >> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >> (M.N.F.Dilhasha) >> Undergraduate | Department of Computer Science and Engineering >> University of Moratuwa >> Sri Lanka >> >> On Thu, May 7, 2015 at 4:38 AM, Fathima Dilhasha <[email protected]> >> wrote: >> >>> Hi Jasintha, >>> >>> Thank you for the valuable suggestions. I'll have a look at WSO2 >>> Developer Studio as well. >>> >>> Thanks. >>> Regards, >>> Dilhasha >>> >>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>> (M.N.F.Dilhasha) >>> Undergraduate | Department of Computer Science and Engineering >>> University of Moratuwa >>> Sri Lanka >>> >>> On Tue, May 5, 2015 at 9:57 AM, Jasintha Dasanayake <[email protected]> >>> wrote: >>> >>>> Similar functionalities have been implemented in the WSO2 Developer >>>> Studio, so you may refer[1] that as well,there you may find some useful API >>>> calls and logics too. >>>> >>>> Thanks and Regards >>>> /Jasintha >>>> >>>> [1] - https://github.com/wso2/developer-studio/tree/master/appfactory >>>> >>>> On Mon, May 4, 2015 at 5:10 PM, Fathima Dilhasha < >>>> [email protected]> wrote: >>>> >>>>> Hi, >>>>> >>>>> As the initial step, I have come up with the following set of basic >>>>> functionalities to be implemented for AppFactory CLI tool considering CLI >>>>> tools available for other platforms ( similar to App Factory ) as well. >>>>> >>>>> *General Commands* >>>>> >>>>> >>>>> - list supported commands >>>>> - manage app creation and deletion >>>>> - list App details >>>>> - authentication to App Factory (login, logout) >>>>> - API Management (listing API keys) >>>>> - Database/Data source management >>>>> >>>>> >>>>> *Application Specific Commands* >>>>> >>>> >>>> >>>> I think there should be command to list the all application first, then >>>> should be a command to get information for a select application. >>>> >>>>> >>>>> >>>>> >>>>> - List information about Application >>>>> - Life Cycle Management for an aplication >>>>> - Display logs for an application >>>>> - Manage App versioning >>>>> - Application User Management >>>>> - Get Latest Build Info for app >>>>> >>>>> This tool will take use of system native shell rather than a separate >>>>> App Factory specific shell. This approach is expected to provide better >>>>> user experience. The tool will be built in 'GO' since it caters for easy >>>>> adoption to different OSs with cross compilation support, easy integration >>>>> of functionalities into system native shell. >>>>> >>>>> Your feedback and suggestions on this approach are highly appreciated. >>>>> >>>>> Thanks. >>>>> >>>>> Regards, >>>>> >>>>> Dilhasha >>>>> >>>>> >>>>> Fathima Dilhasha Nazeer <http://lk.linkedin.com/in/dilhasha/> >>>>> (M.N.F.Dilhasha) >>>>> Undergraduate | Department of Computer Science and Engineering >>>>> University of Moratuwa >>>>> Sri Lanka >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> >>>> *Jasintha Dasanayake* >>>> >>>> *Senior Software EngineerWSO2 Inc. | http://wso2.com >>>> <http://wso2.com/>lean . enterprise . middleware* >>>> >>>> >>>> *mobile :- 0711368118* >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >> > -- *Anuruddha Premalal* Software Eng. | WSO2 Inc. Mobile : +94710461070 Web site : www.regilandvalley.com
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
