@Marvin when updating a file nme used in an existing entrypoint I receive this error. Is there a way to force this to update without manually updating the flows.json file? prefect --no-prompt deploy --name google-cloud-storage Conflicting entry found for flow with name 'cloud-storage-flow'. Existing entrypoint: projects/prefect/test-flows/gcp.py:cloud_storage_flow Attempted entrypoint: projects/prefect/test-flows/gcp-cloud-storage.py:cloud_storage_flow You can try removing the existing entry for 'cloud-storage-flow' from your ~/.prefect/flows.json

It seems that there are currently no open issues on GitHub related to updating the entrypoint and encountering an error with the

flows.json

file. The error message you received suggests that the existing flow registered with Prefect has a different entrypoint compared to the one you're attempting to use now. To resolve this error, you could manually update the

flows.json

file as the error message suggested, or you can try re-registering the flow with the new entrypoint. Unfortunately, there's no Prefect CLI command to force an update without touching the

flows.json

file directly. When registering a flow, Prefect keeps track of flows and their entrypoints in this file, and conflicting information needs to be resolved either manually or by re-registering the flow with the updated entrypoint. If you decide to edit the

flows.json

file, make sure to back up the file first, and then proceed with removing the existing entry for 'cloud-storage-flow' and re-registering your flow with the new entrypoint. If you regularly encounter this issue, it might be worth scripting the process or creating an issue on the Prefect GitHub repository to suggest an improvement to the deployment process.