Open abrookins opened 4 months ago
That makes sense to me that we would want to display that's it's been updated. We should probably do this first and then #12288
Hi, @serinamarie would love to take this one.
Hi @eladm26, are you still interested in this one?
Yeah, hopefully will get into it later this week
On Mon, 15 Apr 2024 at 16:20 Serina Grill @.***> wrote:
Hi @eladm26 https://github.com/eladm26, are you still interested in this one?
— Reply to this email directly, view it on GitHub https://github.com/PrefectHQ/prefect/issues/12287#issuecomment-2056838980, or unsubscribe https://github.com/notifications/unsubscribe-auth/AA6P43GXK56GVJXBWC4UQNLY5PHYVAVCNFSM6AAAAABEUXMK4SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANJWHAZTQOJYGA . You are receiving this because you were mentioned.Message ID: @.***>
Sounds good :)
First check
Bug summary
If I update my
prefect.yaml
file for a deployment previously created withprefect deploy ...
and then runprefect deploy
again to update the deployment (this is how I'm supposed to update from the YAML file), the command reports that it created a deployment:I selected an existing deployment to use, so this is confusing. However, I seem to still only have one deployment with this name, so an update happened but was reported as a creation.
Reproduction
Error
No response
Versions
Additional context
No response