Skip to content

feat(core): Add queue_name parameter to Job.enqueue() method #19424

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

Merged
merged 1 commit into from
May 8, 2025

Conversation

dianbofa
Copy link
Contributor

@dianbofa dianbofa commented May 7, 2025

  • Added the queue_name parameter to Job.enqueue(), allowing users to specify an existing queue name.

  • If queue_name is not provided, the default model queue will be used.

  • This enhancement improves job scheduling flexibility by enabling targeted execution in specific queues.

Fixes: #18419

- Added the queue_name parameter to Job.enqueue(), allowing users to specify an existing queue name.

- If queue_name is not provided, the default model queue will be used.

- This enhancement improves job scheduling flexibility by enabling targeted execution in specific queues.
@jeremystretch jeremystretch requested review from a team and arthanson and removed request for a team May 7, 2025 13:12
@arthanson
Copy link
Collaborator

@dianbofa enqueue function is never called with the queue_name set. Do you see this being used externally by scripts or just for future use?

@dianbofa
Copy link
Contributor Author

dianbofa commented May 8, 2025

@dianbofa enqueue function is never called with the queue_name set. Do you see this being used externally by scripts or just for future use?

The queue_name parameter enables more flexible task queue configuration for external scripts while supporting future system scalability.

@dianbofa dianbofa mentioned this pull request May 8, 2025
@arthanson arthanson merged commit 0c04a8d into netbox-community:main May 8, 2025
3 checks passed
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.

enabling multi-worker parallel task processing
2 participants