401 Error when trying to trigger Airbyte Sync

[gmorrell]

Apache Airflow Provider(s)

airbyte

Versions of Apache Airflow Providers

apache-airflow-providers-airbyte | 5.0.0

Apache Airflow version

2.10.4

Operating System

MacOS (local deployment via docker)

Deployment

Docker-Compose

Deployment details

No response

What happened

When making a sync call using the AirbyteTriggerSyncOperator. I am receiving a 401 error but manual API calls work (to token URL)

During my manual testing i found without the content type header = application/json i would get a 401.

Is the call made in this provider done without this header as it will not work otherwise?

What you think should happen instead

Should get a successful status code back

How to reproduce

try to make a call to airbyte to trigger sync using the Aitbyte connection type with client id and secret

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[bot]]

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.

[potiuk]

I think this is more of a question, than Airlfow issue. And you might want to get more help with your problem if you provide more details - log files, more details on what DAG you have etc. As much information you can get - this might allow someone to help you with your problem.

Remember that this is not a helpdesk. People here are helping others with their problem in their free time (this is an open-source project run by volunteers) and the more information you provide, the higher chance is someone will be able to help you.

[potiuk]

converted to discussion/

[gmorrell]

@potiuk I do believe this to be an issue with a package that is maintained by the airflow team

If i try to dig to the actual API call itself i only see the URL and the payload not any headers been set (see screenshot) and without it every call will fail.

Not really sure why this is not an issue when it is clearly not working

[potiuk]

If you show some logs of this faiure - then yes it might be an issue.

But you seem to be very close to making a fix and testing it - so maybe simply make a PR and fix it. we absolutely do not need issues in order to accept PR fixing a problem. So there is no point in arguing whether things are issues or discussions - if a PR can fix it and you can verify it locally, This is best outcome of it.