I'm having an issue where the prefect SDK is overwriting my logging configuration when the module is loaded. The codebase's logging configuration is partially determined at run time and loaded along with django, so simply specifying the

PREFECT_LOGGING_SETTINGS_PATH

env var doesn't seem sufficient. What's the best way to prevent prefect from making additional changes to the logging configuration when loaded?

Hey @Allie Duff can we please get someone to take a look at this? It’s currently holding us up in our migration to Prefect 2. Thank you!

Relevant enhancement issue: https://github.com/PrefectHQ/prefect/issues/10051