You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dolphinscheduler.apache.org by "github-actions[bot] (via GitHub)" <gi...@apache.org> on 2023/08/22 05:13:05 UTC
[GitHub] [dolphinscheduler] github-actions[bot] commented on issue #14783: [Feature][User] When to add the function of user or role permission
github-actions[bot] commented on issue #14783:
URL: https://github.com/apache/dolphinscheduler/issues/14783#issuecomment-1687440953
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and found no similar feature requirement.
### Description
We have a public computing platform and use the same dolphinscheduler, but there is no concept of user roles in dolphinscheduler, and everyone can create new projects. It is hoped that only administrators or authorized users can create new projects, and other users can only use this project, and users without authorization cannot see this project. Therefore, it is best for users to have: administrators, developers (submitting tasks, running tasks), operation and maintenance personnel (publishing jars, developers can only be in the development environment, and can only operate and maintain officially)
### Use case
_No response_
### Related issues
_No response_
### Are you willing to submit a PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
--
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: commits-unsubscribe@dolphinscheduler.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org