What is the difference between the setting databas...
# ask-ai
r
What is the difference between the setting database: an d externalDatabase: in the helm config
k
Based on the knowledge sources provided, I can explain the difference between the
database:
and
externalDatabase:
settings in the Airbyte Helm configuration: 1.
database:
setting: This is part of the
global:
configuration and is used to specify details for an external database. It's the more recent and recommended way to configure an external database for Airbyte. Example configuration:
Copy code
yaml global:   database:     type: external     secretName: "airbyte-config-secrets"     host: ""     port: ""     database: ""     userSecretKey: ""     passwordSecretKey: ""
2.
externalDatabase:
setting: This is an older configuration method that appears to be deprecated or less preferred. While it's still mentioned in some sources, it's not the primary recommended way to configure an external database. Example configuration:
Copy code
yaml externalDatabase:   host: "<http://my-custom-host.com|my-custom-host.com>"   user: "postgres"   database: "airbyte"   password: ""   existingSecret: "secrets-airbyte-airbyte-webapp-svc-prod"   existingSecretPasswordKey: "airbyte-db-password"   port: 5432
The main differences are: 1. Structure:
database:
is nested under
global:
, while
externalDatabase:
is at the root level of the configuration. 2. Usage: The
global.database
configuration is more commonly referenced in recent documentation and issues. 3. Secret handling: The
global.database
configuration uses separate keys for user and password secrets, while
externalDatabase
has a single
existingSecret
field. It's important to note that the most recent documentation recommends using the
global.database
configuration. For example, the [Airbyte documentation on external databases](https://docs.airbyte.com/deploying-airbyte/integrations/database) specifically shows the
global.database
configuration method. When configuring an external database for Airbyte using Helm, it's recommended to use the
global.database
configuration as shown in the most recent documentation.