Airbyte is an open-source data integration engine that helps you consolidate your data in your data warehouses, lakes and databases.

Airbyte

How do i declare a secret in configurations.yaml which is defined in .octavia secret file?
When i declare as  ${AIRBYTE_PASSWORD} it does not read the actual value from .octavia file, but uses ${AIRBYTE_PASSWORD} as value.
<@U04SE163WC8>
```
configuration:
  host: xxx
  port: xxxxx
  schemas:
  - SCHEMA_XXX
  password: ${AIRBYTE_PASSWORD}
  username: UNAME
  encryption:
    encryption_method: unencrypted
  tunnel_method:
    tunnel_method: NO_TUNNEL
  connection_data:
    service_name: MASTER
    connection_type: service_name```

To use a secret in your `configuration.yaml` file that is defined in your `.octavia` secret file, you need to ensure that the secret is correctly set in the `.octavia` file. The secret should be referenced in the `configuration.yaml` file as `${SECRET_NAME}`.   Here is an example of how to declare a secret in the `configuration.yaml` file:  ```yaml configuration:   password: ${MY_PASSWORD} ```  In this case, `MY_PASSWORD` is an environment variable that you have set. When you run `octavia apply`, it will load the value of `MY_PASSWORD` into the `password` field.  If the secret is not being correctly read from the `.octavia` file, there might be an issue with how the secret is set in the `.octavia` file. Make sure that the secret is correctly defined in the `.octavia` file.  Also, note that when importing resources, Octavia overwrites the environment variables that you configured originally with the real value and replace secrets with '**********'. Given this limitation, you can still version control Airbyte configs, but you won’t be able to push this new configuration to a different instance without editing the secrets in the template and adding the environment variables that may change between instances.  For more information, refer to the [Airbyte CLI documentation](<https://docs.airbyte.com/cli-documentation>) and the [Airbyte tutorial on version control](<https://airbyte.com/tutorials/version-control-airbyte-configurations>).

Sorry <@U05EHUN8HSS>, I seem to be having a bit of trouble. Don't worry though, I've pinged my support folks and they will try to fix me up! :technologist:

Perhaps try again in 5mins?

<@U05EHUN8HSS> - If I read the documentation correctly the secret doesn’t come from the .octavia file it comes from an ENV variable.  In your case you would need an ENV variable named AIRBYTE_PASSWORD

<https://github.com/airbytehq/airbyte/blob/master/octavia-cli/README.md#as-a-command-available-in-your-bash-profile|This sentence is confusing then>, right?

```This script:
Pulls the octavia-cli image from our Docker registry.
Creates an octavia alias in your profile.
Creates a ~/.octavia file whose values are mapped to the octavia container's environment variables.```


what i understand is that ehan i run octavia apply it will pass these vars to server  as environment vars