You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The temporal pod is having difficulty finding a key for the database ending the logs with this message when it boots up:
Unable to load configuration: config file corrupted: yaml: line 11: did not find expected key.
I can connect to the external database from the cluster.
I've deleted everything in the database between deployments just to make sure there's nothing there to trip the installation up.
I'm installing with helm using a values.yaml file.
I've added a secret that has mounted successfully prior with the DATABASE_USER/DATABASE_PASSWORD variables in it.
This deployment process worked with the internal database.
Below are the parts of the values file I think are applicable to this question - am I missing something? Please, any help would be greatly appreciated.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, I am really struggling with configuring an external database on GCP for Airbyte.
I've read the documentation here: https://docs.airbyte.com/operator-guides/configuring-airbyte-db
and have tried a bunch of different ways to configure my values.yaml file, but I'm not getting anywhere.
The temporal pod is having difficulty finding a key for the database ending the logs with this message when it boots up:
Unable to load configuration: config file corrupted: yaml: line 11: did not find expected key.
Below are the parts of the values file I think are applicable to this question - am I missing something? Please, any help would be greatly appreciated.
Beta Was this translation helpful? Give feedback.
All reactions