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 attaches 'ApplicationLifecycle'. But when changing life cycle name of an application as discussed above, the current way of attaching life cycle is not applicable. The solution I found is storing life cycle name as an attribute in the 'appinfo' artifact. Therefore when the user changes the life cycle the 'appinfo' artifact will be as following. <metadata xmlns="http://www.wso2.org/governance/metadata "><application><description></description><name>app10</name><owner> [email protected] </owner><key>app10</key><type>war</type><repoAccessability>perDevRepo</repoAccessability><repositorytype>git</repositorytype><applicationCreationStatus>PENDING</applicationCreationStatus></application> <serviceLifecycle><lifecycleName>New Lifecycle Name</lifecycleName></serviceLifecycle> </metadata> Is it okay if I use the solution I suggested? Your comments are highly valued. Thanks. On Mon, Jun 29, 2015 at 12:04 PM, Bimali Dayananda <[email protected]> wrote: > 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 one life cycle to the app from the > interface provided [1]. > > -The implementation will include followings [2]. > > [1] > https://docs.google.com/a/wso2.com/drawings/d/1-wwZf-4fB9ha6ETJ3ZzO78olVY1rG0GfjqL0kn-NN0o/edit?usp=sharing > [2] > https://docs.google.com/a/wso2.com/document/d/102O0hCwlXd0td2edJ1MBs-Tf9CvMKkf5Grr4ZARyJCc/edit?usp=sharing > > On Fri, Jun 26, 2015 at 2:29 PM, Dimuthu Leelarathne <[email protected]> > wrote: > >> 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 1:47 PM, Dimuthu Leelarathne <[email protected]> >> wrote: >> >>> >>> >>> On Fri, Jun 26, 2015 at 1:46 PM, Dimuthu Leelarathne <[email protected]> >>> 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 test). >>>> >>> >>> But the backend must be completely configurable. >>> >>> >>> >>>> >>>> thanks, >>>> dimuthu >>>> >>>> >>>> On Fri, Jun 26, 2015 at 11:08 AM, Amila Maha Arachchi <[email protected]> >>>> wrote: >>>> >>>>> 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 >>>>> pre-defined runtimes/stages. When this new UI/Feature rolls out, how is it >>>>> going to work in the cloud? >>>>> >>>>> On Mon, Jun 22, 2015 at 3:01 PM, Dimuthu Leelarathne < >>>>> [email protected]> wrote: >>>>> >>>>>> 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 < >>>>>> [email protected]> wrote: >>>>>> >>>>>>> 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 suggested is that we >>>>>>> can >>>>>>> reuse life cycle configurations for multiple apps and we can govern who >>>>>>> can >>>>>>> define life cycle configurations. >>>>>>> >>>>>>> thank you. >>>>>>> >>>>>>> >>>>>>> On Fri, Jun 19, 2015 at 8:29 PM, Bimali Dayananda <[email protected]> >>>>>>> wrote: >>>>>>> >>>>>>>> Hi, >>>>>>>> >>>>>>>> Currently in the AppFactory there are three stages called >>>>>>>> Development, Testing and Production for a life cycle. >>>>>>>> >>>>>>>> Problem: >>>>>>>> The users who create applications can use only the predefined >>>>>>>> stages. >>>>>>>> >>>>>>>> Solution: >>>>>>>> Let the user to decide life cycle stages in each application or >>>>>>>> else they can use the default life cycle. >>>>>>>> >>>>>>>> Below attachments are the rough sketches of flow diagram and the >>>>>>>> interface design I have planned for the task. >>>>>>>> >>>>>>>> Your comments and suggestions are highly valued. >>>>>>>> >>>>>>>> Thank you. >>>>>>>> >>>>>>>> -- >>>>>>>> Bimali Dayananda >>>>>>>> Intern-Software Engineering >>>>>>>> Mobile : +94(77) 571 6618 >>>>>>>> [email protected] >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> Architecture mailing list >>>>>>>> [email protected] >>>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> Manjula Rathnayaka >>>>>>> Software Engineer >>>>>>> WSO2, Inc. >>>>>>> Mobile:+94 77 743 1987 >>>>>>> >>>>>>> _______________________________________________ >>>>>>> Architecture mailing list >>>>>>> [email protected] >>>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> Dimuthu Leelarathne >>>>>> Director & Product Lead of App Factory >>>>>> >>>>>> WSO2, Inc. (http://wso2.com) >>>>>> email: [email protected] >>>>>> Mobile : 0773661935 >>>>>> >>>>>> Lean . Enterprise . Middleware >>>>>> >>>>>> _______________________________________________ >>>>>> Architecture mailing list >>>>>> [email protected] >>>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>>> >>>>>> >>>>> >>>>> >>>>> -- >>>>> *Amila Maharachchi* >>>>> Senior Technical Lead >>>>> WSO2, Inc.; http://wso2.com >>>>> >>>>> Blog: http://maharachchi.blogspot.com >>>>> Mobile: +94719371446 >>>>> >>>>> >>>>> _______________________________________________ >>>>> Architecture mailing list >>>>> [email protected] >>>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>>> >>>>> >>>> >>>> >>>> -- >>>> Dimuthu Leelarathne >>>> Director & Product Lead of App Factory >>>> >>>> WSO2, Inc. (http://wso2.com) >>>> email: [email protected] >>>> Mobile : 0773661935 >>>> >>>> Lean . Enterprise . Middleware >>>> >>> >>> >>> >>> -- >>> Dimuthu Leelarathne >>> Director & Product Lead of App Factory >>> >>> WSO2, Inc. (http://wso2.com) >>> email: [email protected] >>> Mobile : 0773661935 >>> >>> Lean . Enterprise . Middleware >>> >> >> >> >> -- >> Dimuthu Leelarathne >> Director & Product Lead of App Factory >> >> WSO2, Inc. (http://wso2.com) >> email: [email protected] >> Mobile : 0773661935 >> >> Lean . Enterprise . Middleware >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Bimali Dayananda > Intern-Software Engineering > Mobile : +94(77) 571 6618 > [email protected] > -- Bimali Dayananda Intern-Software Engineering Mobile : +94(77) 571 6618 [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
