On Mon, May 28, 2018 at 3:31 PM Bhathiya Jayasekara <[email protected]>
wrote:

> Hi,
>
> On Mon, May 28, 2018 at 3:23 PM, Harsha Kumara <[email protected]> wrote:
>
>> *Core Cli Commands*
>>
>>    - *micro-gw setup/init (with inputs username, label name and
>>    password(*optional
>> *)) *
>>
>> I think the project path shoul be an input for this.
>
Yes

>
>
>> micro-gw-resources
>>
>>     ├── conf
>>
>>     │   └── config.yaml
>>
>>     └── projects (folder name is same as label name)
>>
>>         ├── accounts
>>
>>         │   ├── src
>>
>>         │   │   ├── companyAccounts_v1.0.0.bal
>>
>>         │   │   └── salesforce_v1.0.0.bal
>>
>>         │   └── target
>>
>>         │       ├── accounts.balx
>>
>>         │       └── accounts.zip
>>
>>         ├── finance
>>
>>         │   ├── src
>>
>>         │   │   ├── invoices_v2.0.0.bal
>>
>>         │   │   └── payments_v2.1.0.bal
>>
>>         │   └── target
>>
>>         │       ├── finance.balx
>>
>>         │       └── finance.zip
>>
>>         ├── gateway-config
>>
>>         │   └── gateway-config.yaml
>>
>>
> Shouldn't this come under every label? f
>
Yes structure should be as follow.
micro-gw-resources
    ├── conf
    │   └── config.yaml
    └── projects
        ├── accounts
        │   ├── gateway-config
        │   │   └── gateway-config.yaml
        │   ├── src
        │   │   ├── companyAccounts_v1.0.0.bal
        │   │   └── salesforce_v1.0.0.bal
        │   └── target
        │       ├── accounts.balx
        │       └── accounts.zip
        ├── finance
        │   ├── gateway-config
        │   │   └── gateway-config.yaml
        │   ├── src
        │   │   ├── invoices_v2.0.0.bal
        │   │   └── payments_v2.1.0.bal
        │   └── target
        │       ├── finance.balx
        │       └── finance.zip
        └── sales
            ├── gateway-config
            │   └── gateway-config.yaml
            ├── src
            │   ├── customers_v3.0.0.bal
            │   └── leads_v4.0.0.bal
            └── target
                ├── sales.balx
                └── sales.zip


> Thanks,
> Bhathiya
>
>
>>         └── sales
>>
>>             ├── src
>>
>>             │   ├── customers_v3.0.0.bal
>>
>>             │   └── leads_v4.0.0.bal
>>
>>             └── target
>>
>>                 ├── sales.balx
>>
>>                 └── sales.zip
>>
>>
>>    - *micro-gw build (with inputs label name)*
>>       - This command build single balx out of all APIs belongs to given
>>       label. If docker/kubernetes configurations specified, then archive
>>       will be generated. This archive will embeds bre, generated balx which
>>       someone can take and run without configuring anything.
>>       - This command also outputs APIs which have updated and commands
>>       which are available to run in target folder
>>    - *micro-gw run (with label name)*
>>       - This command will use to run the balx generated for given label.
>>
>> Please share your suggestions and improvements.
>>
>>
>> Thanks,
>> Harsha
>> --
>> Harsha Kumara
>> Associate Technical Lead, WSO2 Inc.
>> Mobile: +94775505618
>> Blog:harshcreationz.blogspot.com
>>
>
>
>
> --
> *Bhathiya Jayasekara*
> *Associate Technical Lead,*
> *WSO2 inc., http://wso2.com <http://wso2.com>*
>
> *Phone: +94715478185*
> *LinkedIn: http://www.linkedin.com/in/bhathiyaj
> <http://www.linkedin.com/in/bhathiyaj>*
> *Twitter: https://twitter.com/bhathiyax <https://twitter.com/bhathiyax>*
> *Blog: http://movingaheadblog.blogspot.com
> <http://movingaheadblog.blogspot.com/>*
>


-- 
Harsha Kumara
Associate Technical Lead, WSO2 Inc.
Mobile: +94775505618
Blog:harshcreationz.blogspot.com
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to