@Marvin When I use a prefect.yaml to deploy multiple flows, the same push_to_s3 step repeatedly runs ones per flow deployment, which slows down the deployment. The push_to_s3 step really only needs to run once. Is there some way to make it so the push_to_s3 only runs once?

It seems there aren't any open GitHub issues that directly address this problem. To achieve the outcome where

push_to_s3

runs only once while deploying multiple flows, consider the following strategy: 1. Use a Control Flow: Modify your deployment logic so that

push_to_s3

is conditionally executed. For instance, you could use a control flow mechanism to check if the S3 push has already been completed for the current deployment session. 2. Use Prefect Task Caching: Prefect tasks can leverage caching so that if the task's inputs haven't changed, it can reuse the previous result rather than executing again. This is especially useful if your

push_to_s3

step doesn't vary across flows or deployments. 3. Create a Separate Deployment Step: Isolate

push_to_s3

from the flow deployment steps and run it as a separate step in your CI/CD pipeline or deployment script. This ensures it's only executed once before deploying the flows. 4. Dependency Management: Set up your flows' tasks in such a way that

push_to_s3

is a dependency for the initial task of each flow and all the flows are deployed in a manner where this condition is checked just once. Without direct experience with Prefect 2.x, I can't give you an exact code snippet, but I can suggest looking into the above strategies and adapting them to your specific deployment process. If you have a unique configuration or if your flows must execute

push_to_s3

in a certain way, consider reaching out on the Prefect community Slack or forums with your specific use case for more tailored advice. Remember to test any changes in a staging environment prior to production to avoid any disruptions. Would you like more detailed guidance on implementing any of these strategies?