Feature 13165

[mxq-151]

Purpose of the pull request

this pr is for issue #13165

Brief change log

1.change rest api in dolphinscheduler-api
2.change mapper in dolphinscheduler-dao
3.add some field mysql table
4.add code in OssOperator

1.add user view

2.project admin view

3.admin user's resource view

4.admin user's project view

5.admin user's run-job view

6.project user' run-job view

[SbloodyS]

Please update the document too.

[mxq-151]

Please update the document too.

I will do it later,would you guys merge this pr without doc?

[SbloodyS]

Please update the document too.

I will do it later,would you guys merge this pr without doc?

It is better to merge with the document.

[mxq-151]

i found authority management have been commited,it is too coarse,it's hard to use,now should i conitnue to update doc to commit this pr?

[mxq-151]

i found authority management have been commited,it is too coarse,it's hard to use,now should i conitnue to update doc to commit this pr?

@SbloodyS some case in use as below
1.Certain users can only access certain workers
2.it cost too much tell admin user to config alert group,alert group should manager by tenant it selft
3.it's dangerous that someone has permission to run a job（who has edit permission can run a job too）

[SbloodyS]

i found authority management have been commited,it is too coarse,it's hard to use,now should i conitnue to update doc to commit this pr?

You can optimize the document in this PR, or you can create a separate PR. The main purpose is that new features need to be consistent in code and documentation.

[mxq-151]

i found authority management have been commited,it is too coarse,it's hard to use,now should i conitnue to update doc to commit this pr?

You can optimize the document in this PR, or you can create a separate PR. The main purpose is that new features need to be consistent in code and documentation.

ok,docs will update soon

[zhongjiajie]

Hi @mxq-151 I personally do not thing OSS project should have complex permission setting, unless the project is design for permission configurations, because each person or company have it own permission need, maybe some config we thing is useful is useless for others.

and unless we make our permission config as complete as possible, to allow user can config whatever they want, but it will cost lots of time to build and test it. And our code base will full of permission code, when user want to add new feature will be difficult

[mxq-151]

Hi @mxq-151 I personally do not thing OSS project should have complex permission setting, unless the project is design for permission configurations, because each person or company have it own permission need, maybe some config we thing is useful is useless for others.

and unless we make our permission config as complete as possible, to allow user can config whatever they want, but it will cost lots of time to build and test it. And our code base will full of permission code, when user want to add new feature will be difficult

it means that you guys will not accept the pr?

[zhongjiajie]

we need more discussions to judge whether we should accept or not. and maybe we will take some of them, or maybe we will merge all of them, but the point is more dicussions

[mxq-151]

Hi @mxq-151 I personally do not thing OSS project should have complex permission setting, unless the project is design for permission configurations, because each person or company have it own permission need, maybe some config we thing is useful is useless for others.

and unless we make our permission config as complete as possible, to allow user can config whatever they want, but it will cost lots of time to build and test it. And our code base will full of permission code, when user want to add new feature will be difficult

What I have done is to delegate some authority to the project administrator to reduce the management cost of the super administrator, which should not be complicated

[mxq-151]

docs have been updated(only chinese language)，path:docs/docs/zh/guide/authority.md

[mergeable]

⚠️ This PR do not change database DDL synchronize.

[mxq-151]

we need more discussions to judge whether we should accept or not. and maybe we will take some of them, or maybe we will merge all of them, but the point is more dicussions

@SbloodyS
how is going about the disccussion now?

[mxq-151]

has any advise about this feature? @SbloodyS