Use a script to kick off a pipeline run.
Details
Details
- Reviewers
• max - Commits
- R1:0636bf0fbb61: Add an example of how to trigger a pipeline by graphQL
test_trigger_pipeline.py
Diff Detail
Diff Detail
- Repository
- R1 dagster
- Lint
Lint Not Applicable - Unit
Tests Not Applicable
Event Timeline
Comment Actions
this is pretty good, couple of nits in the comments. it might be nice to also explain the graphql query a little bit.
| docs/next/src/pages/examples/trigger_pipeline.mdx | ||
|---|---|---|
| 36 | how does the user know what inputs to use for repositoryLocationName and repositoryName? | |
| 37 | helpful to clarify that runConfigData is the same as the run_config parameter to execute_pipeline | |
| 54 | which input? | |
| examples/trigger_pipeline/requirements.txt | ||
| 1 ↗ | (On Diff #31235) | do we need this file if the requirements are specified in setup.py |
| examples/trigger_pipeline/tests/test_trigger_pipeline.py | ||
| 27 | after you send the kill signal, you should proc.wait() to ensure it actually exits | |
| 35 | in general it's helpful to call out magic numbers like this by making them global constants with explicit names like DAGIT_STARTUP_TIMEOUT | |
| 40 | you can use an f-string for this | |
| examples/trigger_pipeline/requirements.txt | ||
|---|---|---|
| 1 ↗ | (On Diff #31235) | Lint has highlighted importing gql problem before for some reason. It should be okay to remove this file now. See updates. |
| examples/trigger_pipeline/tests/test_trigger_pipeline.py | ||
| 35 | This means we should make it clear the 15 is the DAGIT_STARTUP_TIMEOUT. See updates for the change. | |