-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Use worker_pool_name
and worker_pool_queue_name
in deployment API endpoints.
#8031
Conversation
✅ Deploy Preview for prefect-orion ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
worker_pool_name
and worker_pool_queue_name
from deployment API endpoints.worker_pool_name
and worker_pool_queue_name
in deployment API endpoints.
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.
a few minor questions about pool name vs. queue name logic
Replaced with worker_pool_queue_name and worker_pool_name
c51e1d8
to
f0a0acf
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.
This seems reasonable given my limited understanding of API design.
Updates deployment API endpoints to return
worker_pool_name
andworker_pool_queue_name
to better align with worker pool and worker pool queue GET endpoints that use names.Updates deployment create and update API endpoints to accept
worker_pool_name
andworker_pool_queue_name
to eliminate need for clients to interact with IDs for worker pools or worker pool queues.See #8012 for a similar implementation for flow runs.
Example
Checklist
<link to issue>
"fix
,feature
,enhancement