potiuk commented on PR #22698:
URL: https://github.com/apache/airflow/pull/22698#issuecomment-1088602747

   > The approach we have gone elsewhere is to have classes pre-registered via 
plugins, and only allow those to be serialized.
   > 
   > I think I'd rather that over a new config option
   
   Quite agree. Extending Plugins with custom dependencies sounds like a way 
better way of doing it when this is treated as reusable feature that others 
will be able to reason about. 
   
   I think eventually we want to reach the situation (Airflow 3) that DAG 
authors can never ever produce a code that will be executed in the 
contex/machine where scheduler is running. Adding configuration that enables 
that sounds like a bad idea when we rather  do a deliberate effort to gradually 
remove any of such options.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to