[api] Airbyte API does not use AIRBYTE_URL for paging

airbytehq / airbyte

The leading data integration platform for ETL / ELT data pipelines from APIs, databases & files to data warehouses, data lakes & data lakehouses. Both self-hosted and Cloud-hosted.

https://airbyte.com

Other

16.36k stars 4.16k forks source link

[api] Airbyte API does not use AIRBYTE_URL for paging #39420

Open GKTheOne opened 5 months ago

GKTheOne commented 5 months ago

Topic

Airbyte API

Relevant information

We have Airbyte in a Kubernetes cluster, exposed via ingress. Slack notifications use the AIRBYTE_URL in their links. ie, "https://airbyte.our.domain" The Airbyte API is using the pod dns name (and port) in the previous/next paging links. ie, /sources returns a next of "http://airbyte-airbyte-server-svc:8001/api/public/v1/sources?includedDeleted=false&limit=20&offset=20" To not break API clients, I would like it to use the AIRBYTE_URL value instead.

marcosmarxm commented 5 months ago

Thanks @GKTheOne I added this to the team backlog.