-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
hoists the run queue config from the run coordinator up to the instance #26932
Conversation
13f2c3c
to
4710c64
Compare
Deploy preview for dagit-core-storybook ready! ✅ Preview Built with commit f1b7934. |
a068773
to
4d471e9
Compare
4710c64
to
2ce911a
Compare
4d471e9
to
859dd4c
Compare
2ce911a
to
e5e8022
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.
seems very reasonable, the run queue no longer really makes sense as an optional/pluggable component anymore the way it did when this was first added.
859dd4c
to
be163cf
Compare
e5e8022
to
32eec84
Compare
be163cf
to
e7dc76b
Compare
32eec84
to
3ba911e
Compare
e7dc76b
to
5b84e11
Compare
3ba911e
to
2bed622
Compare
5b84e11
to
b5ec0b8
Compare
2bed622
to
253141f
Compare
b5ec0b8
to
6df13a3
Compare
253141f
to
24f23d7
Compare
6df13a3
to
47d228f
Compare
24f23d7
to
16acc11
Compare
47d228f
to
0af051b
Compare
16acc11
to
7dae80e
Compare
0af051b
to
d199ebd
Compare
8649c64
to
f1b7934
Compare
5ea38ab
to
529046e
Compare
f1b7934
to
be7ec05
Compare
Summary & Motivation
For ease of use, #26931 consolidates concurrency settings (including queued run coordinator settings) into a single deployment settings block.
This PR makes it so that run queue settings are now accessed off of the instance, instead of off of the run coordinator.
The run coordinator is a standalone-configured module. This makes it difficult to incorporate instance settings from other places.
How I Tested These Changes
BK