Summary
The user is facing issues configuring Airbyte to use an existing Hashicorp Vault setup in Docker-compose. Despite setting necessary variables in .env file and docker-compose.yaml, they are encountering ‘secret not found’ errors when trying to set or fetch a secret in the Oracle connector. The user has validated that the curl command to fetch secrets from Vault returns the list of secrets, indicating that the issue may not be with environment variables.
Question
Hi guys, having some trouble with getting airbyte through docker-compose configured to use an existing Hashicorp Vault setup- I have set the necessary variables in both the .env file and docker-compose.yaml, but when trying to set or fetch a secret in my Oracle connector, I keep getting the error message “secret not found”, even when entering the actual values I would like to use in the UI rather than the value of the secret. Can someone help me with how I should configure this? I have validated that running the curl command " curl --header “X-Vault-Token: $VAULT_AUTH_TOKEN” --request GET $VAULT_ADDRESS/v1/$VAULT_PREFIX" from within the airbyte-server container returns the list of all of the secrets from the vault, so I don’t think the issue is with my environment variables. The error messages are like the below:
ERROR i.a.c.s.p.VaultSecretPersistence(read):36 - Vault failed on read. Response code: <tel:4032024-10-03|403 2024-10-03> 15:44:59 ERROR i.a.s.a.ApiHelper(execute):49 - Unexpected Exception java.lang.RuntimeException: That secret was not found in the store! Coordinate: airbyte_workspace_…
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.