Triggers are detected off of a graphql mutation, which requires a running dagit server, bypassing any storage layer
Details
Details
Diff Detail
Diff Detail
- Repository
- R1 dagster
- Lint
Automatic diff as part of commit; lint not applicable. - Unit
Automatic diff as part of commit; unit tests not applicable.
Event Timeline
python_modules/dagster-graphql/dagster_graphql/implementation/execution/trigger.py | ||
---|---|---|
40 | check.invariant? (for consistency) |
js_modules/dagit/src/schema.graphql | ||
---|---|---|
637 | maybe we can prefix this with experimental |
js_modules/dagit/src/schema.graphql | ||
---|---|---|
637 | I tend to not think of graphql schema as a public API. This will only have an effect if the trigger is defined, which will generate a warning. |
js_modules/dagit/src/schema.graphql | ||
---|---|---|
637 | agreed. plus a rename causes thrash in terms of rebuilding dagit, regenn'ing ts, etc |