You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "pierrejeambrun (via GitHub)" <gi...@apache.org> on 2026/01/22 17:00:34 UTC

[I] Dag level rbac for backfills [airflow]

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

   ### Body
   
   In #47482 we decided to handle the permission of backfills through a new entity `BackfillDetails` which isn't related to a Dag.
   
   Now I'm second guessing this, because it is currently not possible to do permission filtering based on Dag access. Similarly to other `DagAccessEntity` I think it would be beneficial to be able to filter access to backfills based on Dag permissons. Currently giving access to 'read on DAG:SomeDag' does not give any access on the related backfills. 
   
   ### Committer
   
   - [x] I acknowledge that I am a maintainer/committer of the Apache Airflow project.


-- 
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@airflow.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Dag level rbac for backfills [airflow]

Posted by "vincbeck (via GitHub)" <gi...@apache.org>.
vincbeck commented on issue #60948:
URL: https://github.com/apache/airflow/issues/60948#issuecomment-3785908593

   > The idea is that 'backfills' really exist as a sub entity of a Dag
   
   If that's the case then I agree, it makes total sense to make Backfill not a top level entity but a sub entity of Dag in our auth model.
   
   The small complexity we might have is, many backfill APIs do not have any reference to `dag_id` (e.g. [get_backfill](https://github.com/apache/airflow/blob/main/airflow-core/src/airflow/api_fastapi/core_api/routes/public/backfills.py#L101)) so we might need to make an additional query to get the dag_id and pass it to the auth manager.
   
   Another topic but kind of related, if backfills are really sub entity of Dags, then we should probably have this relation in the api as well. Example: `/api/dag/123/backfill/456` instead of `/api/backfill/456`. And that's true for the other dag sub entities. That's the definition of Rest. But given this is a breaking change, it is probably not worth exploring that.


-- 
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@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Dag level rbac for backfills [airflow]

Posted by "vincbeck (via GitHub)" <gi...@apache.org>.
vincbeck commented on issue #60948:
URL: https://github.com/apache/airflow/issues/60948#issuecomment-3785925551

   If we go down that path I think we need:
   - Deprecate `is_authorized_backfill`
   - Add `Backfill` to `DagAccessEntity`
   - Potentially update auth manager implementation to take into consideration this new value. I do not think this is needed cause no auth manager that I am aware of does case by case logic depending on the value of `DagAccessEntity`
   - Communication to users because if some users are using `KeycloakAuthManager` or `AwsAuthManager`, then they might need to make some modifications to their authz policies


-- 
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@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Re: [I] Dag level rbac for backfills [airflow]

Posted by "jason810496 (via GitHub)" <gi...@apache.org>.
jason810496 closed issue #60948: Dag level rbac for backfills
URL: https://github.com/apache/airflow/issues/60948


-- 
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@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org