Hi all! 👋 I'm doing some work on Dagster's Airbyte integration at the moment: https://github.com/dagster-io/dagster/pull/31867 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. Does anyone know if the Airbyte team intend to keep the API schemas identical, or should we expect these APIs to diverge? We unfortunately are using the Configuration API for one call to get the data types of stream fields, but we can remove that once the

/streams

api includes that information (I did find two issues marked as "complete", but the API still doesn't supply this info [GitHub Issue 41646] [GitHub Issue 44489]).