-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC-557] add example for triggering job with GraphQL endpoint #25288
Conversation
Deploy preview for dagster-docs-beta ready! Preview available at https://dagster-docs-beta-4beiun1cb-elementl.vercel.app Direct link to changed pages: |
) | ||
``` | ||
|
||
### Triggering an asset materialization |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added both asset materialization via LaunchPipelineExecution
and run request with LaunchRunMutation
.
How do we feel about the presentation of these two options?
6a112b7
to
f2afcdc
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to stamp this because I want us to be able to merge it and move forward.
One minor nit that can be done in this PR or a follow up, could we add a breadcrumb from the sensors page (https://dagster-docs-beta-7hhekcwb3-elementl.vercel.app/guides/sensors) to this?
The sensors page is listed as 'event-triggers' in the sidebar, so I think someone might naturally click there. We want them to read about sensors but also know there are other options.
One suggestion for language is to update that page with:
Creating event-based pipelines with sensors
Sensors enable you to trigger Dagster runs in response to events from external systems.
They run at regular intervals, either triggering a run or explaining why a run was skipped. For example, you can trigger a run when a new file is added to an Amazon S3 bucket or when a database row is updated.
:::tip
An alternative to polling with sensors is to push events to Dagster using the Dagster API
Thanks! Added your suggestion to this PR. |
Summary & Motivation
LaunchRunMutation
with the GraphQL endpointHow I Tested These Changes
Created a local Dagster instance containing:
Launched the run using:
The same was done for the asset materialization.
Changelog