[rfc] Document using backfill API from schedules/sensors #27260
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Background
@smackesey has interacted with several users on the following scenario:
Problem Statement
We do not have a good solution to the above scenario.
So if X is a backfill, basically your only option is to use a job that then uses the private GQL API.
Objective
The purpose of this enhancement is to improve user experience. This will allow users to not have to resort to workarounds to perform a manual trigger a conditional launch of X.
The manifestation of this is to expose a public Python API for creating and launching asset backfills.
Specifically, they should be able to launch backfills from schedules and sensors.