Remove scenario name from task queue name #197
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
stephanos
force-pushed
the
simpler-tq
branch
from
10a216c to
744d652
Compare
Sushisource
approved these changes
Sep 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What was changed
Omes client and worker get their task queue only from the RunID now; instead of also the scenario name.
Why?
RunID is already expected to be a unique identifier; scenario name is superfluous. When running multiple scenarios, the user can pick a unique, clear RunID to distinguish them.
This also simplifies the CICD use case where the workers need to be deployed first before the clients are run. That means the name(s) of the scenario(s) need to known and propagated ahead of time. Now all that's needed is a RunID.
Checklist
Closes
How was this tested: