Taragolis commented on issue #35011: URL: https://github.com/apache/airflow/issues/35011#issuecomment-1772027803
@Zhenye-Na Reference to different kind of API https://docs.airbyte.com/api-documentation and their differences - [Configuration API](https://airbyte-public-api-docs.s3.us-east-2.amazonaws.com/rapidoc-api-docs.html), Airflow Provider currently use this one. Endpoints started with `api/v1/{service}` - [Airbyte API](https://api.airbyte.com/), this is a target API. Endpoint started with `v1/{service}`. As far as I could see it is available in OSS since [v0.50.13](https://github.com/airbytehq/airbyte-platform/releases/tag/v0.50.13) Ideally keep both working until it discontinued, because I believe that I'm not the only one who still use v0.4x releases, but personally for me discontinue Airbyte Configuration API in Airflow doesn't affect me. So if it possible, create new Hook (e.g. **AirbyteApiHook** [_conn_type_ = "airbyte_api", _hook_name_ = "Airbyte API", _conn_name_attr_ = "airbyte_api_conn_id", _default_conn_name_ = "airbyte_default"]) which provide thin wrapper around [`airbyte-api-python-sdk`](https://github.com/airbytehq/airbyte-api-python-sdk), new connection type, and create replacement for AirbyteTriggerSyncOperator / AirbyteJobSensor -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
