What area the feature impact?
Connectors
Relevant Information
In airbyte docs when building a custom connector, it states (https://docs.airbyte.com/integrations/custom-connectors) after creation and publishing you can programmatically use a custom connector as a source.
It seems this is only true in airbyte OSS.
In airbyte cloud's API that is currently not available. As stated here - https://airbytehq.slack.com/archives/C021JANJ6TY/p1699913551475239
The airbyte cloud UI builder allows easy creation of api based connectors and UI functionality to create a source from those connectors already. We just want the cloud API to be exposed to do the same.
What area the feature impact?
Connectors
Relevant Information
In airbyte docs when building a custom connector, it states (https://docs.airbyte.com/integrations/custom-connectors) after creation and publishing you can programmatically use a custom connector as a source.
It seems this is only true in airbyte OSS.
In airbyte cloud's API that is currently not available. As stated here - https://airbytehq.slack.com/archives/C021JANJ6TY/p1699913551475239
The airbyte cloud UI builder allows easy creation of api based connectors and UI functionality to create a source from those connectors already. We just want the cloud API to be exposed to do the same.