You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proposed PR creates a single interface for Airbyte Cloud and self-hosted (AirbyteWorkspace and AirbyteClient). Chatting to the dagster team in the background, and we're unsure if we should split these classes out into separate ones (AirbyteCloudWorkspace for cloud, AirbyteWorkspace for self-hosted).
It seems like apart from the API base URLs, the Cloud & Self-hosted APIs are identical right now, and when you're in the OSS Airbyte, it links you to the same API docs as Cloud.
Does anyone know if the Airbyte team intend to keep the API schemas identical, or should we expect these APIs to diverge?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all! 👋
I'm doing some work on Dagster's Airbyte integration at the moment: dagster-io/dagster#31867
The proposed PR creates a single interface for Airbyte Cloud and self-hosted (
AirbyteWorkspaceandAirbyteClient). Chatting to the dagster team in the background, and we're unsure if we should split these classes out into separate ones (AirbyteCloudWorkspacefor cloud,AirbyteWorkspacefor self-hosted).It seems like apart from the API base URLs, the Cloud & Self-hosted APIs are identical right now, and when you're in the OSS Airbyte, it links you to the same API docs as Cloud.
Does anyone know if the Airbyte team intend to keep the API schemas identical, or should we expect these APIs to diverge?
Beta Was this translation helpful? Give feedback.
All reactions