Skip to content

Comments

Deprecate BackfillDetails and use DagAcccessEntity.Run for backfill p…#61400

Merged
vincbeck merged 6 commits intoapache:mainfrom
astronomer:deprecate-backfill-detail-and-use-run-perms-for-backfill
Feb 4, 2026
Merged

Deprecate BackfillDetails and use DagAcccessEntity.Run for backfill p…#61400
vincbeck merged 6 commits intoapache:mainfrom
astronomer:deprecate-backfill-detail-and-use-run-perms-for-backfill

Conversation

@pierrejeambrun
Copy link
Member

@pierrejeambrun pierrejeambrun commented Feb 3, 2026

part of #60948

Deprecate is_authorized_backfill and BackfillDetails in favor of DagAccessEntity.Run.

Basically this will allow dag access level control on backfills, a backfill is always attached to a Dag, and shouldn't probably have been a sub DagAccessEntity in the auth model. We chose to simply re-use the existing DagAccessEntity.Run instead of creating a new one because 'creating a backfill' is basically similar to creating multiple dag runs. (A user with Can create on Dag Runs can simulate a backfill by triggering as many dag runs as needed with the appropriate conf and data).

From now on permissions granted on DagRuns will also allow similar permissions on 'Backfills' of a specific dag id.

Note: I plan a follow up PR for the providers.

  • Did I used AI ? (no)

@pierrejeambrun pierrejeambrun added this to the Airflow 3.1.8 milestone Feb 3, 2026
@pierrejeambrun pierrejeambrun self-assigned this Feb 3, 2026
@pierrejeambrun pierrejeambrun added the backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch label Feb 3, 2026
@boring-cyborg boring-cyborg bot added area:API Airflow's REST/HTTP API kind:documentation labels Feb 3, 2026
@pierrejeambrun pierrejeambrun force-pushed the deprecate-backfill-detail-and-use-run-perms-for-backfill branch from 9ae1916 to d31bfc6 Compare February 4, 2026 08:37
@vincbeck vincbeck merged commit 9b48498 into apache:main Feb 4, 2026
249 of 250 checks passed
@github-actions
Copy link

github-actions bot commented Feb 4, 2026

Backport failed to create: v3-1-test. View the failure log Run details

Status Branch Result
v3-1-test Commit Link

You can attempt to backport this manually by running:

cherry_picker 9b48498 v3-1-test

This should apply the commit to the v3-1-test branch and leave the commit in conflict state marking
the files that need manual conflict resolution.

After you have resolved the conflicts, you can continue the backport process by running:

cherry_picker --continue

If you don't have cherry-picker installed, see the installation guide.

@pierrejeambrun
Copy link
Member Author

Manual backport #61456

pierrejeambrun added a commit to astronomer/airflow that referenced this pull request Feb 4, 2026
jason810496 pushed a commit that referenced this pull request Feb 5, 2026
…r backfill p… (#61456)

* Deprecate BackfillDetails and use DagAcccessEntity.Run for backfill p… (#61400)

(cherry picked from commit 9b48498)

* Fix CI
Alok-kumar-priyadarshi pushed a commit to Alok-kumar-priyadarshi/airflow that referenced this pull request Feb 5, 2026
jhgoebbert pushed a commit to jhgoebbert/airflow_Owen-CH-Leung that referenced this pull request Feb 8, 2026
@jedcunningham jedcunningham deleted the deprecate-backfill-detail-and-use-run-perms-for-backfill branch February 12, 2026 17:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:API Airflow's REST/HTTP API backport-to-v3-1-test Mark PR with this label to backport to v3-1-test branch kind:documentation

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants