airbytehq / airbytehq/airbyte

Helm Chart: make temporal and temporal_visibility databases configurable

Aperta
#11,157 21 commenti 15 reazioni 1 assegnatario Rivendicata da @octavia-squidington-iii Vedi su GitHub
area/platform-oss autoteam community frozen helm help-welcome team/platform-move type/enhancement
Lingua principale
Python
Stelle
22.1k
Fork
5.3k
Metriche di merge delle PR
Metriche PR in attesa

Descrizione

## 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:
```

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.