-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Update deployment overview docs #17612
base: main
Are you sure you want to change the base?
Conversation
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 couple comments to start - one question: why remove the .deploy
example?
I think if we want to keep this page conceptual we should at least link to some concrete examples for those who are looking for immediate answers on how to make deployments
--- | ||
|
||
Deployments allow you to run flows on a [schedule](/v3/automate/add-schedules/) and trigger runs based on [events](/v3/automate/events/automations-triggers/). | ||
A deployment is a server-side store of metadata that enables remote orchestration. It defines when, where, and how a workflow should run. |
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.
personally, I think this opening sentence is more vague than it was before. "enables remote orchestration" of what? I know that we follow up with "a workflow" but since currently deployments are server-side configuration records for flows specifically, I think we should remain concrete in our description.
- [scheduling](/v3/automate/add-schedules): You can set deployments to run manually, on a schedule, or in response [events](/v3/automate/events/automations-triggers). | ||
- Remote management: Deployments expose an API and UI that allow you to trigger new runs, cancel active runs, pause scheduled runs, and customize parameters remotely. | ||
- Infrastructure configuration: Deployments inherit infrastructure settings from work pools, which can be overridden at creation or runtime. | ||
- Metadata storage: They store important information about the flow, enabling remote orchestration and management. |
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.
is this last bullet distinct from the existing ones?
[Work pools](/v3/deploy/infrastructure-concepts/work-pools/) allow you to switch between different types of infrastructure and to create a template for deployments. | ||
Data platform teams find work pools especially useful for managing infrastructure configuration across teams of data professionals. | ||
### Prototyping and local processes | ||
To run flows in a local process, there are two options. The `.serve()` method can be useful for prototyping quickly; it couples the creation of a deployment and the creation of a process worker. Use a worker with a [process work pool](/v3/deploy/static-infrastructure-examples/docker) on long-lived remote infrastructure, such as a VM or EC2 instance. |
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.
its confusing to me that we'd say "long-lived remote infrastructure" in a section titled "local processes"
|
||
<Note> | ||
**You don't have to commit to one approach** | ||
Only the Python SDK supports the `.serve()` method. While deployments cannot be created via the UI, they can be edited, or deleted. Prefect. |
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.
hrm, stray Prefect here?
Only the Python SDK supports the `.serve()` method. While deployments cannot be created via the UI, they can be edited, or deleted. Prefect. | |
Only the Python SDK supports the `.serve()` method. While deployments cannot be created via the UI, they can be edited, or deleted. Prefect. |
Co-authored-by: nate nowack <thrast36@gmail.com>
Co-authored-by: nate nowack <thrast36@gmail.com>
Updates deployment overview page to add more context and explanation.
Checklist
<link to issue>
"mint.json
.