g-dailey opened a new issue, #55841: URL: https://github.com/apache/airflow/issues/55841
### Apache Airflow Provider(s) airbyte ### Versions of Apache Airflow Providers `apache-airflow-providers-airbyte==5.2.3` ### Apache Airflow version 3 ### Operating System Operating System: Debian GNU/Linux 12 (bookworm) (via Astro Runtime 3.0.10 container) ### Deployment Astronomer ### Deployment details I am using Astro Runtime 3.0.10 for local development (Docker). I also tested with Astro Runtime 12.5.0 and 13.2.0. In those runtimes, the Airbyte provider page shows the correct fields (`client_id` and `client_secret`). However, in Airflow 3, those fields are missing and replaced with the standard connection fields. <img width="646" height="547" alt="Image" src="https://github.com/user-attachments/assets/3caba0ba-afeb-4468-b1a9-60a065869c19"; /> ### What happened When using `apache-airflow-providers-airbyte==5.2.3` with Airflow 2, the provider correctly requires the `client_id` and `client_secret` fields. However, in Airflow 3, these fields are missing and instead replaced by the standard connection fields (host, login, password, port, schema). This mapping is incorrect for Airbyte connections. I also attempted to add `client_id` and `client_secret` under `Extra JSON Fields`, but the connection still failed between Airbyte and Airflow. ### What you think should happen instead The `client_id` and `client_secret` fields should be available to use Airbyte connection successfully. ### How to reproduce Add `apache-airflow-providers-airbyte==5.2.3` to your Airflow 3 deployment and attempt to create Airbyte Connection to see the missing fields. ### Anything else _No response_ ### Are you willing to submit PR? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
