@kapa.ai we switched to chart 2.0.19, so we have airbyte 2.0.1 community edition running. We would like to test Custom components in the connector builder, but the feature is missing

Custom Components in the Connector Builder are disabled by default and must be explicitly enabled at the deployment level. For Airbyte 2.x (including 2.0.1) you need to: 1. Add the following to your

values.yaml

(Helm v2 style keys shown first, v1 style below it): [Custom components]

# Helm chart v2 keys
   workloadLauncher:
     extraEnv:
       - name: AIRBYTE_ENABLE_UNSAFE_CODE
         value: "true"
   connectorBuilderServer:
     extraEnv:
       - name: AIRBYTE_ENABLE_UNSAFE_CODE
         value: "true"

or (Helm chart v1):

workload-launcher:
     extraEnv:
       - name: AIRBYTE_ENABLE_UNSAFE_CODE
         value: "true"
   connector-builder-server:
     extraEnv:
       - name: AIRBYTE_ENABLE_UNSAFE_CODE
         value: "true"

2. Upgrade/redeploy Airbyte with that file, for example: [Custom components]

helm upgrade airbyte airbyte-v2/airbyte \
     --namespace airbyte \
     --values ./values.yaml

After this, the Custom Components feature should appear in the Connector Builder UI. Note that the docs emphasize this feature is UNSAFE and EXPERIMENTAL and allows execution of arbitrary code in your environment, so use it only in trusted/self-managed setups. [Custom components] 👍 0 button 👎 0 button ℹ️ Tip: Mention @kapa.ai in the thread for follow-ups or DM the app for 1-to-1 help.