Hi all, our use-case with Airbyte is to embed it in our SaaS product, and use it’s API internally to create connections, but also load runtime status of connections and jobs to visualize it in our own UI. I don’t think we need source and destination be in namespace, but just connections (in our use case). I heard about the workspace/namespace concept to separate our tenants/customers connections natively, so that loading data is always tenant-separated. I saw activities around creating/listing/deleting workspaces (https://github.com/airbytehq/airbyte/issues/1735) but could not see (on a first glimpse)

wordpaceId

params in all other API endpoints. Is this currently a feature we should rely on, or should we (for now) develop a naming scheme for connections (can connections even have a name today?)?

@Siamak Haschemi the workspace concept is relevant in a few scenarios that I suspect will be helpful for you: • when creating sources/destinations

sources/create

and

destinations/create

• when listing connections/sources/destinations

Thank you! Will look at it.

My guess is you would have a workspace per customer and keep the mapping of customer id to workspace id on your side then use it accordingly