potiuk commented on PR #40775: URL: https://github.com/apache/airflow/pull/40775#issuecomment-2237334624
> Have some doubs if somebody has concerns with traceability as the configuration of the hook has side effe cts to the runtime of the DAG as the GIT hash of your DAG code does not clearly show which dependencies you had. For people concerned with this, they should not use the hook. Good that it is optional and requirements can be added on DAG code as well. I am still uneasy even without test option. The tracability, yes. It **feels** wrong to have dependencies moved aside of the DAG code, it's not really the "idea" behind the connection - connection was not supposed to change anything in the environment and all the parameters were supposed to refer to 'external system'. I have a feeling that we are trying to see the nail when we have a hammer at hand. There is a good reason why there was no Python Hook in the first place. -- 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]
