ashb commented on a change in pull request #7563: [AIRFLOW-6939] Executor configuration via import path URL: https://github.com/apache/airflow/pull/7563#discussion_r385131154
########## File path: UPDATING.md ########## @@ -61,6 +61,29 @@ https://developers.google.com/style/inclusive-documentation --> +### Custom executors is loaded using full import path + +In previous versions of Airflow it was possible to use plugins to load custom executors. It is still +possible, but the configuration has changed. Now you don't have to create a plugin to configure a +custom executor, but you need to provide the full path to the module in the `executor` option +in the `core` section. The purpose of this change is to simplify the plugin mechanism and make +it easier to configure executor. + +If your module was in the path `my_acme_company.executors.MyCustomExecutor` and the plugin was +called `my_plugin` then your configuration looks like this + +```ini +[core] +executor = my_plguin.MyCustomExecutor Review comment: Oh wow missed that one totally! ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
