This was originally in place as part of the feature flagging mechanism for
events and automations, but is probably too aggressive for 3.0. Similarly to
managing deployments even if PREFECT_API_SERVICES_SCHEDULER_ENABLED is turned
off, we can allow people to turn off triggers but still manage automations.
This was originally in place as part of the feature flagging mechanism for events and automations, but is probably too aggressive for 3.0. Similarly to managing deployments even if
PREFECT_API_SERVICES_SCHEDULER_ENABLEDis turned off, we can allow people to turn off triggers but still manage automations.