Hello, is there a way to prevent deployments from overriding whether or not a flow is enabled in Prefect 1? In this case, I have deployed flows that have been turned off in the UI that will automatically be turned on again the next time I deploy changes even for something unrelated. This means having to remember to turn a flow off again after every deployment which can be annoying and create issues if a flow runs by accident when it shouldn't.
Thank you, looks like I need to write some additional logic around the flow registration step in my deployment to avoid scheduling if the flow has previously been deployed
Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.