[Bug] Running dbt compile can overwrite seed files

[Myles1]

Is this a new bug in dbt-core?

• I believe this is a new bug in dbt-core
• I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior

Running dbt compile can overwrite source files with the newly compiled sql

Expected Behavior

Source files will not be changed

Steps To Reproduce

1. Create a new dbt environment
2. Create a dbt_project.yml in another directory
3. Edit the paths in dbt_project.yml to point to the absolute paths in your dbt project
4. Run dbt compile

Relevant log output

No response

Environment

- OS:MacOS 14.5 (23F79)
- Python:3.11.7
- dbt:1.9.0-b2

Which database adapter are you using with dbt?

bigquery

Additional Context

It looks like I'm not the first to experience this (https://discourse.getdbt.com/t/seeds-overwrites-csv-file-if-outside-directory-containing-yml-files/12972) but I couldn't find a fix anywhere

[dbeatty10]

@Myles1 Thanks for reporting this, linking to relevant thread in Discourse, and opening a PR (#10887) 🏆

I was able to reproduce this using the project files and commands below.

Reprex

dbt_project.yml

# other dbt_project.yml content here

seed-paths: ["/full/absolute/path/to/dbt/project/seeds"]

seeds/my_seed.csv

id
1

Commands:

dbt seed
dbt seed

The first command succeeded for me, but the 2nd didn't because the seed file had been overwritten. The file at seeds/my_seed.csv should have been unchanged.

Instead, it overwrote the file which led to an error like this for the 2nd command:

01:21:22    Compilation Error in seed my_seed (/full/path/seeds/my_seed.csv)
  Row 7 has 4 values, but Table only has 1 columns.
  
  > in macro materialization_seed_default (macros/materializations/seeds/seed.sql)
  > called by seed my_seed (/full/path/seeds/my_seed.csv)

[dbeatty10]

@Myles1 I'm curious if you got this error when running dbt compile, because I could only trigger it when I ran dbt seed or dbt build (along with an absolute path for seed-paths)?

[Myles1]

@Myles1 I'm curious if you got this error when running dbt compile, because I could only trigger it when I ran dbt seed or dbt build (along with an absolute path for seed-paths)?

I was able to get dbt compile to overwrite source files by using an absolute path to models