Hi Airbyte Team! Do you guys plan to update the Connector Builder sources to work with all workspaces instead of just the one that created the connector? We found that using the config API we actually can create sources in all workspaces using the connector created in one specific workspace but the one thing that breaks is the frontend API. The

/source_definitions/list_for_workspace

and

/get_for_workspace

routes does not include the created connector in other workspaces except the one that created it. It may rely in the table

actor_definition_workspace_grant

table in the internal postgres database Airbyte uses (and because of unique constraint we can’t modify the table to give grant to more workspaces). We want to use that connector in all workspaces and actually view it in frontend, is that a technical limitation or you plan to modify it in the future?

@Natik Gadzhi is this something you can answer? 😄

Haha, that's a cool workaround you figured out @Matheus Barbosa. Long-term, yes. I'm not sure if it's in 2 months of 5 months, but we will soon make Builder to be able to export a yaml with some supporting data, and file a PR against our repo where automated tooling will get us enough confidence, and then @Marcos Marx (Airbyte) and my team will be able to merge them quickly and thus propagate them to registry and make them available to folks faster.