You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Dakshika Jayathilaka <da...@wso2.com> on 2014/10/05 22:47:49 UTC
Maintain list of sample json files
Hi Devs,
Most of the time we need to maintain separate set of sample JSON to test
things. Also
documentation won't up to date due to rapid changes happens on dev
environment.
Shall we maintain sample JSON set inside tools folder. When any developer
changing things they can easily update sample JSONs as a part of
implementation process. Otherwise other developer needs to check beans or
schema to verify changes.
WDYT?
Thank you,
Regards,
*Dakshika Jayathilaka*
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
Re: Maintain list of sample json files
Posted by Chamila De Alwis <ch...@wso2.com>.
Hi,
I currently have these files[1] versioned to be available whenever I deploy
a new installation.
AFAIK JSON file validation schema are enabled now, so can't we make use of
those components instead of using an end to end test with the REST api's?
[1] - https://github.com/chamilad/stratos-policies
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
On Mon, Oct 6, 2014 at 10:27 AM, Shiroshica Kulatilake <sh...@wso2.com>
wrote:
>
> We already have a set of scripts under the following location
> stratos/tools/rest-api-client added by Imesh I think - Sorry for not
> looking for this first
>
> So we could probably extend this set to cover all scenarios and first run
> this in non-build mode and then take it to build mode ?
>
> IF we add this to the build we will also have to
> 1. Set up Stratos with the required configurations
> 2. Run the scenario scripts - including different flavours as suggested by
> Manula
> 3. Clean up as well - e.g. subscriptions that would spawn instances etc
>
> On Mon, Oct 6, 2014 at 10:18 AM, Manula Chathurika Thantriwatte <
> manulac@wso2.com> wrote:
>
>> Hi,
>>
>>
>> On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake <sh...@wso2.com>
>> wrote:
>>
>>> Hi,
>>>
>>> So - what is the guarantee that when something changes the relevant JSON
>>> file will also be changed ?
>>>
>>
>> Yes. This can be a problem. Because some of the configurations can be
>> different among the IaaS such as zone and region.
>>
>>>
>>> I am totally +1 for having these files plus including them in
>>> documentation - however - not sure whether we will tend to not update these
>>> again.
>>>
>>
>> Yes. Having the common JSON files against the release. Already we have
>> that in the wiki.
>>
>>>
>>> So - how about having this in some format which breaks if the correct
>>> JSON file is not there and the easiest example I can think of is tests.
>>>
>>> For starters can we have a simple script which would invoke all the REST
>>> APIs using sample JSON files and add this to the build ?
>>>
>>
>> +1 for add this to build.
>>
>>>
>>>
>>> WDYT ?
>>>
>>> Thank you,
>>> Shiro
>>>
>>>
>>>
>>> On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>>
>>>>
>>>> +1 for the idea. Only basic samples are available in docs.
>>>> Shall we have a sample directory in root level where it is easy to find
>>>> , users might not search for samples in tools directory.
>>>>
>>>>
>>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>>
>>>
>>>
>>>
>>> --
>>> Shiroshica Kulatilake
>>>
>>> Architect,
>>> WSO2, Inc. http://wso2.com/
>>> Phone: +94 776523867
>>>
>>
>>
>>
>> --
>> Regards,
>> Manula Chathurika Thantriwatte
>> Software Engineer
>> WSO2 Inc. : http://wso2.com
>> lean . enterprise . middleware
>>
>> email : manulac@wso2.com / manula@apache.org
>> phone : +94 772492511
>> blog : http://manulachathurika.blogspot.com/
>>
>>
>>
>>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>
Re: Maintain list of sample json files
Posted by Shiroshica Kulatilake <sh...@wso2.com>.
We already have a set of scripts under the following location
stratos/tools/rest-api-client added by Imesh I think - Sorry for not
looking for this first
So we could probably extend this set to cover all scenarios and first run
this in non-build mode and then take it to build mode ?
IF we add this to the build we will also have to
1. Set up Stratos with the required configurations
2. Run the scenario scripts - including different flavours as suggested by
Manula
3. Clean up as well - e.g. subscriptions that would spawn instances etc
On Mon, Oct 6, 2014 at 10:18 AM, Manula Chathurika Thantriwatte <
manulac@wso2.com> wrote:
> Hi,
>
>
> On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake <sh...@wso2.com>
> wrote:
>
>> Hi,
>>
>> So - what is the guarantee that when something changes the relevant JSON
>> file will also be changed ?
>>
>
> Yes. This can be a problem. Because some of the configurations can be
> different among the IaaS such as zone and region.
>
>>
>> I am totally +1 for having these files plus including them in
>> documentation - however - not sure whether we will tend to not update these
>> again.
>>
>
> Yes. Having the common JSON files against the release. Already we have
> that in the wiki.
>
>>
>> So - how about having this in some format which breaks if the correct
>> JSON file is not there and the easiest example I can think of is tests.
>>
>> For starters can we have a simple script which would invoke all the REST
>> APIs using sample JSON files and add this to the build ?
>>
>
> +1 for add this to build.
>
>>
>>
>> WDYT ?
>>
>> Thank you,
>> Shiro
>>
>>
>>
>> On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
>>
>>>
>>> +1 for the idea. Only basic samples are available in docs.
>>> Shall we have a sample directory in root level where it is easy to find
>>> , users might not search for samples in tools directory.
>>>
>>>
>>> Touched, not typed. Erroneous words are a feature, not a typo.
>>>
>>
>>
>>
>> --
>> Shiroshica Kulatilake
>>
>> Architect,
>> WSO2, Inc. http://wso2.com/
>> Phone: +94 776523867
>>
>
>
>
> --
> Regards,
> Manula Chathurika Thantriwatte
> Software Engineer
> WSO2 Inc. : http://wso2.com
> lean . enterprise . middleware
>
> email : manulac@wso2.com / manula@apache.org
> phone : +94 772492511
> blog : http://manulachathurika.blogspot.com/
>
>
>
>
--
Shiroshica Kulatilake
Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
Re: Maintain list of sample json files
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake <sh...@wso2.com>
wrote:
> Hi,
>
> So - what is the guarantee that when something changes the relevant JSON
> file will also be changed ?
>
Yes. This can be a problem. Because some of the configurations can be
different among the IaaS such as zone and region.
>
> I am totally +1 for having these files plus including them in
> documentation - however - not sure whether we will tend to not update these
> again.
>
Yes. Having the common JSON files against the release. Already we have
that in the wiki.
>
> So - how about having this in some format which breaks if the correct JSON
> file is not there and the easiest example I can think of is tests.
>
> For starters can we have a simple script which would invoke all the REST
> APIs using sample JSON files and add this to the build ?
>
+1 for add this to build.
>
>
> WDYT ?
>
> Thank you,
> Shiro
>
>
>
> On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
>>
>> +1 for the idea. Only basic samples are available in docs.
>> Shall we have a sample directory in root level where it is easy to find ,
>> users might not search for samples in tools directory.
>>
>>
>> Touched, not typed. Erroneous words are a feature, not a typo.
>>
>
>
>
> --
> Shiroshica Kulatilake
>
> Architect,
> WSO2, Inc. http://wso2.com/
> Phone: +94 776523867
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: Maintain list of sample json files
Posted by Shiroshica Kulatilake <sh...@wso2.com>.
Hi,
So - what is the guarantee that when something changes the relevant JSON
file will also be changed ?
I am totally +1 for having these files plus including them in documentation
- however - not sure whether we will tend to not update these again.
So - how about having this in some format which breaks if the correct JSON
file is not there and the easiest example I can think of is tests.
For starters can we have a simple script which would invoke all the REST
APIs using sample JSON files and add this to the build ?
WDYT ?
Thank you,
Shiro
On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
> +1 for the idea. Only basic samples are available in docs.
> Shall we have a sample directory in root level where it is easy to find ,
> users might not search for samples in tools directory.
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
--
Shiroshica Kulatilake
Architect,
WSO2, Inc. http://wso2.com/
Phone: +94 776523867
Re: Maintain list of sample json files
Posted by Manula Chathurika Thantriwatte <ma...@wso2.com>.
Hi,
Previously we have EC2 and OpenStack sample JSON files in tools directory.
But currently there are not available. We can categorize sample JSON files
with the Stratos release version. Some of the sample JSON files which I'm
using for testing can be found in [1].
[1] https://github.com/manulachathurika/Apache_Stratos_JSON_Files
Thanks !
On Mon, Oct 6, 2014 at 7:49 AM, Udara Liyanage <ud...@wso2.com> wrote:
>
> +1 for the idea. Only basic samples are available in docs.
> Shall we have a sample directory in root level where it is easy to find ,
> users might not search for samples in tools directory.
>
>
> Touched, not typed. Erroneous words are a feature, not a typo.
>
--
Regards,
Manula Chathurika Thantriwatte
Software Engineer
WSO2 Inc. : http://wso2.com
lean . enterprise . middleware
email : manulac@wso2.com / manula@apache.org
phone : +94 772492511
blog : http://manulachathurika.blogspot.com/
Re: Maintain list of sample json files
Posted by Udara Liyanage <ud...@wso2.com>.
+1 for the idea. Only basic samples are available in docs.
Shall we have a sample directory in root level where it is easy to find ,
users might not search for samples in tools directory.
Touched, not typed. Erroneous words are a feature, not a typo.
Re: Maintain list of sample json files
Posted by Chamila De Alwis <ch...@wso2.com>.
On Mon, Oct 6, 2014 at 2:17 AM, Dakshika Jayathilaka <da...@wso2.com>
wrote:
> Shall we maintain sample JSON set inside tools folder. When any developer
> changing things they can easily update sample JSONs as a part of
> implementation process.
+1 on the idea.
Regards,
Chamila de Alwis
Software Engineer | WSO2 | +94772207163
Blog: code.chamiladealwis.com
RE: Maintain list of sample json files
Posted by "Martin Eppel (meppel)" <me...@cisco.com>.
+1
Great idea,
Thanks
Martin
From: Dakshika Jayathilaka [mailto:dakshika@wso2.com]
Sent: Sunday, October 05, 2014 1:48 PM
To: dev
Subject: Maintain list of sample json files
Hi Devs,
Most of the time we need to maintain separate set of sample JSON to test things. Also
documentation won't up to date due to rapid changes happens on dev environment.
Shall we maintain sample JSON set inside tools folder. When any developer changing things they can easily update sample JSONs as a part of implementation process. Otherwise other developer needs to check beans or schema to verify changes.
WDYT?
Thank you,
Regards,
Dakshika Jayathilaka
Software Engineer
WSO2, Inc.
lean.enterprise.middleware
0771100911
Re: Maintain list of sample json files
Posted by Nirmal Fernando <ni...@gmail.com>.
+1 and we need to document this in developer guide :)
On Mon, Oct 6, 2014 at 2:17 AM, Dakshika Jayathilaka <da...@wso2.com>
wrote:
> Hi Devs,
>
> Most of the time we need to maintain separate set of sample JSON to test
> things. Also
> documentation won't up to date due to rapid changes happens on dev
> environment.
>
> Shall we maintain sample JSON set inside tools folder. When any developer
> changing things they can easily update sample JSONs as a part of
> implementation process. Otherwise other developer needs to check beans or
> schema to verify changes.
>
> WDYT?
>
> Thank you,
>
> Regards,
>
> *Dakshika Jayathilaka*
> Software Engineer
> WSO2, Inc.
> lean.enterprise.middleware
> 0771100911
>
--
Best Regards,
Nirmal
Nirmal Fernando.
PPMC Member & Committer of Apache Stratos,
Senior Software Engineer, WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/