Hi Bimali,
What you are trying to do requires more work to be useful for AF. We need
to now look at the three lifecycle types.
Production only (The default)
Dev -> Production
Dev->Test->Production
Lets consider Production only. Here we need to allow the person to modify
code in Production and
Hi Anuruddha,
We are not giving the facility to user about deciding check list items or
the life cycle flow.
*We will provide the user three preconfigured life cycles. They will be
like below.
1. 1st-only with prod stage
Hi Bimali,
Need to clarify few facts.
When we say configurable life cycles how much of control are we providing
to the user in configuring the life cycle?
* Can the user decide on TODO check list before promoting from one stage to
another?
* Can the user decide who can promote/demote from one
Hi,
Bit change in the plan. Instead of updating 'appinfo' artifact, attaching
life cycle to the 'appinfo' artifact is done.
Thanks.
On Mon, Aug 10, 2015 at 1:44 PM, Bimali Dayananda bim...@wso2.com wrote:
Hi,
This is regarding changing life cycle name for an application.
Currently in AF
Hi,
This is regarding changing life cycle name for an application.
Currently in AF the life cycle is attached to the application version
artifact the creation of the application versions. If the app is uploaded
then it attaches 'UploadableApplicationLifeCycle' and if the app is created
then it
Hi,
After discussing the issues when implementing configurable life cycle
stages, finally we agreed on followings.
- To have 3 preconfigured lifecycles with following stages.
1. prod only
2. dev and prod
3. dev, test and prod
-After creating the app user can assign
Hi,
After discussing the issues when implementing configurable life cycle
stages, finally we agreed on followings.
- To have 3 preconfigured lifecycles with following stages.
1. prod only
2. dev and prod
3. dev, test and prod
-After creating the app user can assign
Hi,
IMO, we should only let the people add dev and test stages, and by default
apps should have production stage only (as discussed in strategy). So yes
we need to redo the UI to be better (only to add dev and test).
thanks,
dimuthu
On Fri, Jun 26, 2015 at 11:08 AM, Amila Maha Arachchi
On Fri, Jun 26, 2015 at 1:46 PM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi,
IMO, we should only let the people add dev and test stages, and by default
apps should have production stage only (as discussed in strategy). So yes
we need to redo the UI to be better (only to add dev and
Hi all,
Shall we have a preconfigured set of lifecycle? For example something as
below,
sc1.xml - prod only
sc2.xml - dev test prod
sc3.xml - test prod
So in that way people associate the correct lifecycle xml based on the UI
element the person picks.
thanks,
dimuthu
On Fri, Jun 26, 2015 at
Question to AF team:
At the moment, there is a runtime associated with each lifecycle stage.
i.e. Dev for Dev, Test for Test etc. This is not going to change, right? My
concern is, when a user adds a new stage, how are we going to provide the
runtime for it? In the public cloud scenario, we have
Hi Bimali,
In AF, we have roles for the particular stage/stages right? For example
Application Owner/Developer/QA/DevOp etc. How do we handle that if the user
uses custom staging?
Thanks,
-Ayash
On Mon, Jun 22, 2015 at 3:01 PM, Dimuthu Leelarathne dimut...@wso2.com
wrote:
Hi,
IMO, we need
Hi,
IMO, we need to simplify app creation as much as possible to make it user
friendly.
thanks,
dimuthu
On Mon, Jun 22, 2015 at 9:59 AM, Manjula Rathnayake manju...@wso2.com
wrote:
Hi Bimali,
Regarding the attached flow,
Instead of adding more stages while creating the application, can we
Hi Bimali,
Regarding the attached flow,
Instead of adding more stages while creating the application, can we enable
a page to define life cycle configurations. Then at the time of application
creation, user can select one of those life cycle configurations. The
advantage over what you have
14 matches
Mail list logo
