Skip to content
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

58 utilize a single job submission queue instead of having one queue per workflow type #60

Conversation

lfse-slafleur
Copy link
Member

@lfse-slafleur lfse-slafleur commented Jul 26, 2024

…eue for all workflow types and return an error if a job submission is received which uses an unknown workflow type.
…e_subscription to new name declare_queue_and_add_subscription
@lfse-slafleur lfse-slafleur self-assigned this Jul 26, 2024
@lfse-slafleur
Copy link
Member Author

Ready for review except that it is waiting on the SDK to be released. Therefore, draft for now. Once SDK version is released with Project-OMOTES/omotes-sdk-python#61 merged, this will be finalized.

@lfse-slafleur lfse-slafleur marked this pull request as ready for review August 1, 2024 12:26
@lfse-slafleur lfse-slafleur merged commit 2115a2c into main Aug 26, 2024
7 checks passed
@lfse-slafleur lfse-slafleur deleted the 58-utilize-a-single-job-submission-queue-instead-of-having-one-queue-per-workflow-type branch August 26, 2024 07:40
@lfse-slafleur lfse-slafleur restored the 58-utilize-a-single-job-submission-queue-instead-of-having-one-queue-per-workflow-type branch August 26, 2024 09:07
@lfse-slafleur lfse-slafleur deleted the 58-utilize-a-single-job-submission-queue-instead-of-having-one-queue-per-workflow-type branch August 26, 2024 09:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Utilize a single job submission queue instead of having one queue per workflow type
3 participants