Control DAG Executor Assignment through RBAC

[PVK222]

Description

Use RBAC to check DAG owner executors. This enhancement would ensure that only authorized users/processes can access an executor.

Use case/motivation

Preventing unauthorized DAG to access an isolated executor / better DAG and ressource isolation.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[eladkal]

DAGs already have access control feature

airflow/airflow/models/dag.py

Lines 429 to 430 in f2e2221

	:param access_control: Specify optional DAG-level actions, e.g.,
	"{'role1': {'can_read'}, 'role2': {'can_read', 'can_edit', 'can_delete'}}"

Please elaborate on your use case

[PVK222]

Can I limit a DAG to acces to a specifique executor only ?

[PVK222]

The use case is the following one :

Executor 1: dedicate to Department A

Executor 2: Dedicate to Department B

DAG of Developpeur X can only access Executor 1.

[PVK222]

I closed the feature request. thank to Gemini, I thought the DAG could indicate a specific executor and that you could have many executors on Airflow.