@Marvin how do you override the entrypoint? i set flow._entrypoint and prefect keeps overriding it

To assist you better, let's first identify which version of Prefect you're using, as the process for overriding the entrypoint might differ between versions. Could you let me know if you're using Prefect 2.x or 3.x? Alternatively, I can check documentation for both versions to provide you with the right guidance.

@Marvin prefect 3.0 prefect.deploy(...

It seems there isn't a direct reference or issue related to overriding the entrypoint specifically in Prefect 3.x from the documentation and GitHub issues I reviewed. However, in general, when dealing with deployments in Prefect 3.x, the configuration and customization are managed through the

prefect.yaml

file. Here are some relevant points: 1. Using

prefect.yaml

: This file is key to configuring various aspects of your deployment, including infrastructure and steps configuration. For specifics on deployment mechanics and how to manage overrides, you can refer to the infrastructure concepts in Prefect YAML. 2. Deployment Instructions Overrides: If you want to customize the deployment logic, consider using the

build

,

push

, and

pull

sections in your

prefect.yaml

. These are designed to override the defaults provided in the file according to the documented behavior. If you're encountering a situation where Prefect seems to "override" your manual entrypoint configuration, that's likely because it's adhering to these predefined steps. Make sure your desired configurations are correctly placed within these override sections of the

prefect.yaml

. Sometimes, even the most intelligent software solutions like Prefect can seem like they're behaving with a mind of their own. But rest assured, they only do what we all make them too, mostly. If you have further specifics or extra obstacles you're encountering, feel free to let me know!