Hi all, Please note that only change with respect to existing permission model is that, appOwner is not allowed to create runtime configs in Testing and Production stages. Configs will be copied at the time of promotion/deployment of application in Testing and Production stages.
However, the permissions related to databases will not be changed from existing model where each stake holders of runtime environments are allowed to create databases in their environments. eg. QA can create databases on Testing but not in Production. thank you. On Tue, Feb 10, 2015 at 11:04 AM, Amalka Subasinghe <[email protected]> wrote: > Hi All, > > I'm going to do the following changes to the runtime configs (datasources, > properties, external apis) > > - Create/update/read permissions will be as shown in the table after this > fix. > > - The tenant admin also have similar permissions as appowner; he can only > create in development stage and then resources will be propagated to the > testing and production environments via promoting. > So, "create resources in all environments" checkbox, is not valid anymore, > I'm removing it. > > > > > development testing production > appowner create x > > > > update x x x > > read x x x > > > > > > > dev create x > > > > update x > > > > read x x > > > > > > > > qa create > > > > > update > x > > > read x x > > > > > > > > devops create > > > > > update > > x > > read > x x > > > > > > > admin create x > > > > update x x x > > read x x x > > Thanks > Amalka > > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- Manjula Rathnayaka Software Engineer WSO2, Inc. Mobile:+94 77 743 1987
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
