Skip to content

Container launcher not using airbyte-gcs-log-creds #68177

@film42

Description

@film42

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

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions