airbytehq / airbytehq/airbyte

Container launcher not using airbyte-gcs-log-creds

未關閉
#68,177 3 則留言 0 個 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.18

### What step the error happened?

Other

### Relevant information

When a a container is launched, the pod is using the env `GOOGLE_APPLICATION_CREDENTIALS=/secrets/gcp-creds/gcp.json` but it's not using the `airbyte-gcs-log-creds`, it's using the main `airbyte-airbyte-secrets` which doesn't have `gcp.json`.

The pods fail to start because `/secrets/gcp-creds/gcp.json` is not found.

For now I added a custom transformation to slot in a `gcp.json` into `airbyte-airbyte-secrets`.

```
def fix_double_base64_google_application_creds(obj, opts):
if (
obj["kind"] == "Secret"
and obj["metadata"]["name"] == "airbyte-airbyte-secrets"
):
value = obj["stringData"]["GOOGLE_APPLICATION_CREDENTIALS_JSON"]

if not "client_id" in value:
json_value = base64.b64decode(value).decode("utf-8")
obj["stringData"]["GOOGLE_APPLICATION_CREDENTIALS_JSON"] = json_value

# HACK: There is some config mismatch in Airbyte so we'll set this here explicitly
obj["stringData"]["gcp.json"] = json_value

```

### Relevant log output

```shell

```

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

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

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