Hi @Marvin is there a way to globally disable prefect? I'm in the process of decorating our codebase and configuring prefect and I'd like to be able to merge my changes without (yet) forcing other folks at the company to emit prefect data, even to a local server, until I've fully tested it to be sure it doesn't interfere with anything or otherwise behave in surprising ways, in our codebase.

Disabling Prefect globally isn't directly supported, but you can manage its behavior using profiles and configurations. Here's a strategy you might consider: 1. Profiles: Use Prefect profiles to manage different environments. You can create a profile that points to a non-existent or local server, effectively disabling communication with a production server. More on profiles can be found here: Prefect Profiles. 2. Deferred Tasks: You can defer task execution, which allows you to control when tasks are executed. This might help in testing without triggering actual task execution. More details on deferred tasks can be found here: Deferred Tasks. 3. Task Workers: If you're using task workers, simply not starting them will prevent tasks from being executed. Task workers run deferred tasks and report results back to the API, but if they're not running, tasks won't execute. 4. Flow Engine: You could potentially cancel all tasks in a flow using methods like

cancel_all_tasks

, though this would require some direct manipulation of the flow's task runner. These methods should help you test Prefect in your codebase without affecting others. For implementation, you may need to dive into the specific Prefect configurations and commands. If you need more detailed guidance, feel free to ask!