New message text here

If you supply

--profiles-dir

(or

-p

) and Elementary still looks at

.dbt

in your home directory, there are a few things to check based on the knowledge sources: 1. Make sure you are passing the directory, not the file. The

--profiles-dir

flag should point to the directory containing

profiles.yml

, not the file itself. For example, use:

edr report --profiles-dir /path/to/your/.dbt/

and not

edr report --profiles-dir /path/to/your/.dbt/profiles.yml

Passing the file instead of the directory will not work and can cause Elementary to fall back to the default location, as seen in user reports [Slack thread](https://slack.com/archives/C02CTC89LAX/p1678710882384149). 2. Relative vs. absolute paths. If you use a relative path, ensure it is correct relative to your current working directory. Sometimes, using an absolute path can resolve issues with path resolution, especially in containerized or CI environments [Slack thread](https://slack.com/archives/C02CTC89LAX/p1663360805477199). 3. Elementary version or platform-specific issues. There have been reports that in some versions (e.g., 0.16.1 on Ubuntu), Elementary may not respect the

--profiles-dir

flag and still look in the home directory. This appears to be a bug introduced in newer versions, as previous versions (e.g., 0.15.2) worked as expected. The issue may be related to how dbt's internal API changes the working directory after running certain commands [GitHub issue](https://github.com/elementary-data/elementary/issues/1666). 4. Workarounds and troubleshooting: - Try using an absolute path for

--profiles-dir

. - If possible, downgrade to a version where this bug is not present (e.g., 0.15.2). - Double-check that the directory you specify actually contains

profiles.yml

. If after these checks it still does not work, it may be due to a known bug in the current version of Elementary, particularly on Linux/Ubuntu, as described above. In that case, you may need to wait for a fix or use a workaround such as placing

profiles.yml

in the default location. If you have more details about your environment or version, that could help narrow down the issue further.