Hi We will be changing the behaviour on how resources/data-sources will be created in each stages.
Current behaviour is that when a user ( - a Developer) with relevant permission creates an resource/datasource it will be created in all stages. Relevant users needs to modify the values for each stage that they own. For example : DevOps users will change values in Production stage, while QA user(s) changes in 'Testing' stage. Flaw in above model is that a User(s) is implicitly changing the environments he/she don't have access ( for example: Developer creates a resource in production environment). Now the change we are going to introduce is as follows: 1. A users (who has permission) can create an resource/data source only in a initial stage ( - Initial Stage is defined as a stage not having a previous stage. e.g. Development). 2. When a user promotes an application version AF will not deploy new artifact ( currently it does) 3. Once promoted users owning the new stage needs to explicitly deploy the artifact in that stage. During this action Appfactory will check if there are new resources were introduced to previous stage and copy them to current. (Yes in order for this to happen current user needs read access to previous stage. In our opinion this is better than the scheme we have now) 4. Optionally, when demoting an application version Appfactory can un-deploy that from the stage. This will make sure that user needs to deploy the application explicitly when the application version is promoted ( therefore ensuring AF copies any additional resources introduced as explained in Step 3). Thoughts? -- Ramith Jayasinghe Technical Lead WSO2 Inc., http://wso2.com lean.enterprise.middleware E: [email protected]
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
