airbytehq / airbytehq/airbyte

Is it possible to use a local connector registry instead of a remote one ?

未關閉
#71,050 4 則留言 3 個 reaction 已指派 0 人 在 GitHub 檢視
area/platform autoteam community needs-triage team/compose team/platform-move type/bug
主要語言
Python
星號
22.1k
分支
5.4k
平均合併
5 小時
30 天內合併 PR
671

描述

### Helm Chart Version

2.0.19

### What step the error happened?

On deploy

### Relevant information

airbyte-bootloader pods failing in bootstrap phase during connection to the remote connector registry
the value of the following env var is set as follows:
CONNECTOR_REGISTRY_SEED_PROVIDER: remote
This is the default by the chart.
We are running on an air-gapped environment.
Is there a way to circumvent this phase ?
Are we able to supply the json file that is being retrieved by other means ?

### Relevant log output

```shell
2025-12-30 10:15:39,757 [main] INFO i.a.b.DefaultPostLoadExecutor(execute):30 - Updating connector definitions
2025-12-30 10:15:40,215 [main] ERROR i.a.b.ApplicationKt(main):28 - Unable to bootstrap Airbyte environment.
java.lang.RuntimeException: Failed to fetch remote connector registry
at io.airbyte.config.specs.RemoteDefinitionsProvider.getRemoteConnectorRegistry(RemoteDefinitionsProvider.kt:214)
at io.airbyte.config.specs.$RemoteDefinitionsProvider$Definition$Intercepted.$$access$$getRemoteConnectorRegistry(Unknown Source)
at io.airbyte.config.specs.$RemoteDefinitionsProvider$Definition$Exec.dispatch(Unknown Source)
at io.micronaut.context.AbstractExecutableMethodsDefinition$DispatchedExecutableMethod.invoke(AbstractExecutableMethodsDefinition.java:456)

Thank you!
```

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。