Hey all, does anyone know if its possible to change the output format of the `prefect.deployments.de...
s
Hey all, does anyone know if its possible to change the output format of the
prefect.deployments.deploy
function? I can see there are issues with it, but Prefect helpfully truncates the error message to a single character -_-
n
hi @Samuel Hinton! i've opened this PR which refactors
deploy
just a tad in a way that would allow (if merged) customization of the
Table
produced by
deploy
- would that be what you're looking for? you could then create the columns with whatever settings for things like
min_width
that'd be good for your specific case
s
Hmmm, so I can see the patching should work, however, my concern with this is that I feel like legible logging of failures should be guaranteed by the output, instead of requiring a patch. Given this uses rich, I went through the rich codebase and found the Console should respect an environment variable
COLUMNS
and by setting that to 160 in my pipeline I can now see fun details. If you dont want to expose a
display_width: int | None = None
in the deploy functions, maybe at least some doco about how to expand this? 🙂
n
catjam yeah we could add an admonition for that in the CLI docs - thank you!
also hmm, that 422 seems like schema mismatch, older client that has `forbid`den extras
s
Yeah I locally have 2.19.4 and server has 2.19.2, 2.18.1 Im just waiting on our infra team to wake up and approve the pipeline to update the cloud image and Im hoping it all goes away 🙂 EDIT to put correct versions, look like the pipeline to update to 2.19.2 failed the other day so we're still on 2.18.1
n
oh okay, thanks for the versions! ill check into this tomorrow
s
Just commenting to let you know I edited the above comment (in case you had written the versions down somewhere)
🙏 1