[Bug]: Unable to use .env file as expected

[RubenCerna2079]

What happened?

The DAB documentation states that we should put the .env file next to the config file, however, the .env file is not used unless it is in the same directory as where we run the command dab start.

Unsure if it is an issue related to the feature or to documentation.

https://learn.microsoft.com/en-us/azure/data-api-builder/concept/config/env-function#:~:text=Keep%20.env%20adjacent%20to%20dab%2Dconfig.json%20(or%20wherever%20your%20startup%20process%20expects%20it).

Version

2.0.0-rc

What database are you using?

Azure SQL

What hosting model are you using?

Local (including CLI)

Which API approach are you accessing DAB through?

No response

Relevant log output

Code of Conduct

• I agree to follow this project's Code of Conduct

[Aniruddh25]

.env is expected to be in the same directory from where you run the dab start command - i.e. the current working directory. This is explained by the comment in docs: wherever your startup process expects it. The doc can be worded better to mention it should be in the current working directory.