Oliver Tedder
12/10/2024, 12:24 PMSuccessfully created/updated all deployments!
Deployments
┏━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━┳━━━━━━━━━┓
┃ Name ┃ Status ┃ Details ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━╇━━━━━━━━━┩
│ run/myrun │ applied │ │
└─────────────────────────┴─────────┴─────────┘
To schedule a run for this deployment, use the following command:
$ prefect deployment run 'run/myrun'
Marvin
12/10/2024, 12:24 PMprefect.yaml
or via any immediate command line options.
Both Prefect 2.x and 3.x documentation discuss deployment mechanics, but they don't go into specifics about output suppression after deployment. This output is likely part of the standard feedback, designed to assist users by providing the next steps, such as how to schedule a run.
If the output is problematic in environments like CI/CD, a potential workaround could be to redirect the output to null
or handle it in a way that doesn’t affect your logs. This isn't a built-in feature but a common technique in command-line operations.
For more detailed insights, you can have a peek at the Prefect documentation:
- Prefect 2.x: Deployment Guide
- Prefect 3.x: Prefect Deployment Guide
If this continues to be a need, you might consider raising an issue or feature request on the Prefect GitHub repository to explore the possibility of adding such a feature.