[Bug] Specifying compute doesn't work in models imported via dbt packages

[jelstongreen]

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

When a dbt package is installed in a project that contains a model with a databricks_compute config assigned , that compute is not used by the invoking dbt project.

Expected Behavior

Compute should be used regardless of if the model is imported or native to the invokinf project.

Steps To Reproduce

Create a test model with a Databricks compute specified in the model level config different to the default compute to the rest of the project. Run it as part of a dbt project and verify it runs on its specified compute. Now move the model to an imported package and try again. It will run on the default compute instead of the specified compute.

Relevant log output

Environment

- OS:
- Python:
- dbt: 1.8.8

Which database adapter are you using with dbt?

spark

Additional Context

No response