Radeity commented on issue #13395: URL: https://github.com/apache/dolphinscheduler/issues/13395#issuecomment-1407389238
> > Hi @SbloodyS, after further consideration, i think it's inappropriate to support authorize resources in tenant management, for following reasons: > > * Resource binds with tenant by `fullName`, which means after creating resource, it belongs to a specific tenant. > * It doesn't exist the conception of `authorization` any more. One resource can only belong to one tenant. > > Thus, i will make other **changes** when log in as ADMIN: > > * First, remove resources authorization in user management. > * Second, support data migration in resource management, admin can choose the destination tenant, then it simply copies datas from `baseDir` of one tenant to another. > > <img alt="image" width="1432" src="https://user-images.githubusercontent.com/45198818/213612902-084fdb8b-2508-49fd-a0d0-88c6f0fa9625.png";> > > * Third, admin can see all resources from deprecated resource table and resources belong to all tenants. **HOWEVER**, `t_ds_relation_resources_user` and `t_ds_relation_udfs_user` will no longer in use, users have to migrate old resources to new tenant for using them. About this point, we may have to send a email to notify all users. > > > Keep the old resources and remove old authority, it's a more smooth transition. If you agree with that, i'll work on this from now on. Hi, @SbloodyS , what do you think of this proposal? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
![https://user-images.githubusercontent.com/45198818/213612902-084fdb8b-2508-49fd-a0d0-88c6f0fa9625.png"](https://user-images.githubusercontent.com/45198818/213612902-084fdb8b-2508-49fd-a0d0-88c6f0fa9625.png"){kind=link}