jscheffl commented on PR #41314: URL: https://github.com/apache/airflow/pull/41314#issuecomment-2303065500
I think the current behavior is not well and deserves an extension. Actually I am wondering how it ever worked because in SnowflakeHook also a private key is expected (like you would see in SSH) and JSON would also be non-appropriate. So thanks for providing an extension. I just believe it is at the wrong moment of time. We are currently planning to move on to a Airflow 3 release. For this we need to re-work especially the connection form widgets. So all efforts here would need to be thrown away for Airflow 3. Alongside also we are only accepting new features for Airflow 3, means the code you want to contribute will never go live. Probably (Except we miserably fail in planning or change our mind). We defined Airflow 2.10 being the last feature release in the Airflow 2 line and plan only to cut patch releases from there. I assume we need to put this on the wish list for Airflow 3 and also would be happy if you like to contribute there. But as said, the UI is planned to be fully re-written, which also will affect the connection form. Basics are not settled so as of today it is a bit too early to show something off. -- 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]
