[wip] delete backfills via daemon

[jamiedemaria]

Summary & Motivation

Adds a new DELETING status for backfills. adds a condition to the backfill daemon so it can delete all runs associated with a backfill, then delete the backfill for backfills with the DELETING status

• If a backfill moves from REQUESTED to DELETING partway through an iteration, it the backfill will see that it is no longer requested

  dagster/python_modules/dagster/dagster/_core/execution/asset_backfill.py

  Line 802 in 75d9d72

  if backfill.status != BulkActionStatus.REQUESTED:

  and then break the iteration. on the next iteration, the backfill will be deleted

How I Tested These Changes

new unit test

Changelog

Insert changelog entry or delete this section.

[jamiedemaria]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Graphene endpoint for deleting a backfill #25166
• [wip] delete backfills via daemon #25230 👈
• storage endpoint for deleting backfills #25165
• Backfill retries #23679 : 2 other dependent PRs (#25137 , #25167 )
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @jamiedemaria and the rest of your teammates on Graphite

[github-actions]

Deploy preview for dagit-core-storybook ready!

✅ Preview
https://dagit-core-storybook-8kdt9qs38-elementl.vercel.app
https://jamie-backfill-delete-via-daemon.core-storybook.dagster-docs.io

Built with commit 253761c.
This pull request is being automatically deployed with vercel-action

[jamiedemaria]

@gibsondan can i get a quick pass on this to make sure it's heading in the general correct direction?

[jamiedemaria]

todo: need to figure out how this status will be displayed in the UI since we convert backfill statuses to corresponding run statuses but there is no run status that aligns perfectly