You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instructions for setting up a worker are always included when deploying a deployment.
Successfully created/updated all deployments!
Deployments
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┓
┃ Name ┃ Status ┃ Details ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━┩
│ example-flow/Local Dev (chris-brown) │ applied │ │
└──────────────────────────────────────┴─────────┴─────────┘
To execute flow runs from this deployment, start a worker in a separate terminal
that pulls work from the 'local-dev-docker-chris-brown' work pool:
$ prefect worker start --pool 'local-dev-docker-chris-brown'
To schedule a run for this deployment, use the following command:
$ prefect deployment run 'example-flow/Local Dev (chris-brown)'
You can also run your flow via the Prefect UI: https://<redacted>
Describe the proposed behavior
Do not include the details for the setup of the worker if the deployment was to a healthy work-pool with existing workers running
Successfully created/updated all deployments!
Deployments
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┓
┃ Name ┃ Status ┃ Details ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━┩
│ example-flow/Local Dev (chris-brown) │ applied │ │
└──────────────────────────────────────┴─────────┴─────────┘
To schedule a run for this deployment, use the following command:
$ prefect deployment run 'example-flow/Local Dev (chris-brown)'
You can also run your flow via the Prefect UI: https://<redacted>
Example Use
No response
Additional context
We found that the current behaviour is quite confusing to new users coming to an existing setup with working workers.
I discussed issue with Chris (CTO) at the London PACC and it was his suggestion for the enhancement, so he might have already raised an issue for this, so apologies if this is a duplicate. Would be great to have this for the next release of the self-hosted cloud from the perspective of Genomics England
The text was updated successfully, but these errors were encountered:
Describe the current behavior
Instructions for setting up a worker are always included when deploying a deployment.
Describe the proposed behavior
Do not include the details for the setup of the worker if the deployment was to a healthy work-pool with existing workers running
Example Use
No response
Additional context
We found that the current behaviour is quite confusing to new users coming to an existing setup with working workers.
I discussed issue with Chris (CTO) at the London PACC and it was his suggestion for the enhancement, so he might have already raised an issue for this, so apologies if this is a duplicate. Would be great to have this for the next release of the self-hosted cloud from the perspective of Genomics England
The text was updated successfully, but these errors were encountered: