We need to think about how this feature would work in a real scenario 1. An application owner would want to create an app where no code is created but instead an executable that needs to be deployed is uploaded 2.-a This application needs to go through the usual acceptance testing - so it goes through the lifecycle stages 2-b. This is an application which has been tested in a different environment and the user simply wants to deploy it in production 3. The app owner would want to retire it someday
So we need to ideally support 2a and 2b - 2a would be following the usual story we have - 2b will require changes On Fri, May 16, 2014 at 10:27 PM, Ramith Jayasinghe <[email protected]> wrote: > my feeling is that we could go through governance process ( a.k.a Having > the uploaded War file in Devlopement Stage first and user promotes it to > Production). > Main Reason: > think about a scenario where only devOps team has the access to > Production stage. Does would mean DevOps team could create an application > (just to upload this war file). that would complicate our governance story > (and the permission model). > > besides I guess we don't have to support it unless a user asks for it. > thoughts ? > > > > On Fri, May 16, 2014 at 5:57 PM, Punnadi Gunarathna <[email protected]>wrote: > >> Hi All, >> >> App Factory currently supports uploading a WAR file via 'Add New >> Application'. >> >> As per the current implementation we have a config file which has >> ApplicationLifecycle aspect (refer the attachment for more details). >> Therefore when an application >> is added out of a WAR file, the initial stage is set to "Development". >> >> So my concern is whether the WAR file should go through all the life >> cycle stages (Promote/Demote) as an ordinary application or should it >> directly go to "Production" stage. >> >> If we go-ahead with all life cycle stages, then it requires minimal set >> of changes. >> If the requirement is to set the life cycle state as "Production" there >> are two ways to achieve this requirement: >> >> 1. One way is to keep the existing aspect and when the war is created do >> internal calls('Promote') at application update itself to take the >> application to "Production" stage. >> 2. Define another aspect config for WAR files and godhead with it. >> >> Please share your thoughts. >> >> -- >> Thanks and Regards, >> >> Punnadi Gunarathna >> Senior Software Engineer, >> WSO2, Inc.; http://wso2.com <http://wso2> >> Blog: http://hi-my-world.blogspot.com/ >> Tel : 94 11 214 5345 >> Fax :94 11 2145300 >> >> >> >> <http://lalajisureshika.blogspot.com/> >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > Ramith Jayasinghe > Technical Lead > WSO2 Inc., http://wso2.com > lean.enterprise.middleware > > E: [email protected] > P: +94 776715671 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- Shiroshica Kulatilake Architect, WSO2, Inc. http://wso2.com/ Phone: +94 776523867
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
