airbytehq / airbytehq/airbyte

Helm Chart: make temporal and temporal_visibility databases configurable

Aberta
#11,157 21 comentários 15 reações 1 responsável Reivindicada por @octavia-squidington-iii Ver no GitHub
area/platform-oss autoteam community frozen helm help-welcome team/platform-move type/enhancement
Linguagem predominante
Python
Estrelas
22.1k
Forks
5.4k
Merge médio
5h
PRs com merge (30d)
671

Descrição

## Tell us about the problem you're trying to solve
I'm willing to use the same postgresql instance/RDS for multiple Airbyte deployments.
To achieve this I have to preconfigure the databases such as airbte_db_1 airbte_db_2.
But - its not the only dependency, Airbyte deployment requires `temporal_visibility` and `temporal` databases as well ,but I can't preconfigure these when using helm chart deployment.

## Describe the solution you’d like
I'd like to have configuration sections for these databases just like the configuration for externaldatabase:
```
externalTemporalDatabase:
host: localhost
user:
password: ""
existingSecret: ""
existingSecretPasswordKey: ""
database: airbyte_temporal_1
port:

externalTemporalVisibilityDatabase:
host: localhost
user:
password: ""
existingSecret: ""
existingSecretPasswordKey: ""
database: airbyte_temporal_vis_1
port:
```

Guia de contribuição

Abrir o guia de contribuição

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.