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-poli
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 t
Hi,
On Mon, Oct 6, 2014 at 10:06 AM, Shiroshica Kulatilake
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 r
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 whic
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/manulac
+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.
+1 and we need to document this in developer guide :)
On Mon, Oct 6, 2014 at 2:17 AM, Dakshika Jayathilaka
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
> environm
+1
Great idea,
Thanks
Martin
From: Dakshika Jayathilaka [mailto:daksh...@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'
On Mon, Oct 6, 2014 at 2:17 AM, Dakshika Jayathilaka
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 | WS
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 JS
10 matches
Mail list logo