orsagiv94 opened a new issue, #23638:
URL: https://github.com/apache/airflow/issues/23638

   ### Description
   
   When creating/updating Airflow role for a specific team,
   when need to define his permissions for a set of DAGs whose relevant to that 
team, we'll have to add **manually** each relevant permission for each 
associated DAG's name ( = number of permissions X number of DAGs).
   
   
   we need the ability to define role permissions based on DAG's Owner name 
which will reduce a lot of manual work for the Admin maintainers and will 
minimize the number of permissions defined on each role.
   
   ### Use case/motivation
   
   In our organization, we are running Airflow as a workflow manager for about 
~20 teams.
   Each team manages its own DAGs, and we as Admins are the maintainers of all 
of their roles.
   
   Every new DAG must be mentioned in his relevant team-based role twice (for 
read & edit permissions).
   
   So in order to create a new role for team 'A' for example which has 10 DAGs, 
we'll have to create a role with at least 20 permissions which had to be 
defined manually.
   
   in our organization, every DAG has an Owner defined on his DAG's python file.
   Therefore, assigning permissions to a role by DAG's Owner instead of DAG's 
names will reduce significant manual maintenance work and be much more 
efficient. 
   
   example - 
   when setting a role, the permission - 
   `read on DAG:tutorial` can be replaced with `read on OWNER:Team_A`
   
   ### 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://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
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]

Reply via email to