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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
