[Providers] Airbyte new deployment version changed API endpoints

[baugarcia]

Apache Airflow Provider(s)

airbyte

Versions of Apache Airflow Providers

apache-airflow-providers-airbyte==3.5.1

Apache Airflow version

2.8.1

Operating System

MWAA/AL

Deployment

Amazon (AWS) MWAA

Deployment details

Standard MWAA deployment. Nothing really specific or particular

What happened

After updating to one of the latest Airbyte versions (and using acbtl installation method, as they have as standard on their documentation) the Airbyte provider from Airflow cannot connect to the api server. The reason is that the endpoints have changed, according to Airbyte's documentation:

airbytehq/airbyte#43423

https://reference.airbyte.com/reference/standalone-server-deprecation-and-migration-to-airbyte-server

What you think should happen instead

Provider should be updated so that it points to the correct endpoint of the new api for Airbyte server

How to reproduce

Deploy MWAA. Perform a fresh install of Airbyte using current documentation and standards for OSS installation (abctl).
Use Airflow's Airbyte provider to do anything in the Airbyte server and you will get a connection refused error, as it is pointing to the wrong endpoint.

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[Lee-W]

@josix I think you might be interested in this one 🙂

[josix]

Yeah, let me check it

[marcosmarxm]

#41122 implement the new Auth API method.

[Lee-W]

Thanks for letting us know! Let me reassign it to you