Trying to make a cross-project reference to the production environment of an existing project

Help
1

I am trying to make a cross-project reference to the production environment of an existing project. The project I am referencing has a staging environment, so dbt points my references to the staging environment of the upstream project. Is there a way to point to the production environment of the upstream project instead?

I am trying to do this because we don’t refresh the data in the staging environment regularly, but if people developing in the downstream project are pointing at the staging environment to build their objects, then we will be forced to schedule regular refreshes of the staging environment (which would be costly in our case)

I have searched the internet and the community forums but can’t find a way to configure my project dependency reference to point to the production environment. From what I am reading, if a staging environment exists then dbt will point to / reference the staging environment and I can’t configure it to behave differently.

2

Here are the quick rules of how this works:
> 1. Downstream PROD resolves to Upstream PROD.
> 2. Downstream Non-PROD resolves to:
a. If STG exist in Upstream - resolve to Upstream STG.
> i. Even if there hasn’t been a run in STG yet
> b. If STG doesn’t exist in Upstream - resolve to Upstream PROD.

Note: @Jeremy Yeo originally posted this reply in Slack. It might not have transferred perfectly.

3

Thank you for the response. I am looking for a way to override the default behavior. Is there a config setting to force my project to reference the production instance of the upstream project?