ashb commented on issue #17931: URL: https://github.com/apache/airflow/issues/17931#issuecomment-911477694
The main reason I've previously gone down the "require classes the scheduler/webserver will load to require registration" is I have medium term plans to allow a dag definition to be submitted via an API (i.e. an Airflow user to post a JSON blob) -- and I don't want to open that up to allowing reverse-shell or similar by creating an instance of a random class. -- 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]
