Hi David, I assume you know and have digested the documentation in https://github.com/apache/airflow/blob/main/PROVIDERS.rst#accepting-new-community-providers we have?
If it is a generic functionality I think it is fair to raise the disucssion. It might be very minimal. If you use LDAP just for querying... I would fear a bit that the name might be mis-leading if it would be called "ldap" because many would assume it is an authentication/authorization backend? In your case it is a data source like any other SQL, correct? Jens On 12.12.24 11:18, Blain David wrote:
Hello, At our company we developed an LDAPHook based on the open-ldap library (using the python-ldap wrapper dependency), which allows us to executed search queries on our ldap and use that data in our DAG’s to do further processing on it. The reason why I wrote this hook is because I’ve first searched through the airflow repo and didn’t find a provider and thus no hook for it. The only thing I could find was this ldap reference in the following document: https://github.com/apache/airflow/blob/3e2b5e2f54ea3b3695e6576313f87460fb098830/docs/apache-airflow/extra-packages-ref.rst#L64 So my question is, would there be acceptance to introduce an (open)ldap provider in Airflow which offers a Hook and LDAP conn type? At the moment our implementation only offers a search functionality which behind the scenes does a paged lookup for given base, filter, attributes, scope and page_size, which for us was sufficient in what we wanted to achieve, but that could of course be expanded with more functionality if needed. Kind regards, David ** *David Blain* Data Engineer /at/ ICT-514 - BI End User Reporting
