Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify users should run producer project in staging to resolve cross project ref #5799

Closed
1 task done
mirnawong1 opened this issue Jul 18, 2024 · 1 comment · Fixed by #6215
Closed
1 task done
Assignees
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows priority: medium Fix or enhancement to existing information that’s creating some requests from customers

Comments

@mirnawong1
Copy link
Contributor

mirnawong1 commented Jul 18, 2024

Contributions

  • I have read the contribution docs, and understand what's expected of me.

Link to the page on docs.getdbt.com requiring updates

We should clarify that dbt mesh fetches public model information from the producer's staging environment instead of production. the logic should fetch from staging if the consumer is in staging and from production if the consumer is in production.

For more context and details, refer to internal slack thread.

What part(s) of the page would you like to see updated?

https://docs.getdbt.com/docs/collaborate/govern/project-dependencies#how-to-write-cross-project-ref

https://docs.getdbt.com/guides/mesh-qs?step=1

Additional information

No response

@mirnawong1 mirnawong1 added content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows priority: medium Fix or enhancement to existing information that’s creating some requests from customers labels Jul 18, 2024
@mirnawong1 mirnawong1 self-assigned this Sep 26, 2024
@mirnawong1
Copy link
Contributor Author

Mirna to review this and address

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content Improvements or additions to content improvement Use this when an area of the docs needs improvement as it's currently unclear priority: high Technical inaccuracy, missing/incorrect information, or broken links. Negatively affects workflows priority: medium Fix or enhancement to existing information that’s creating some requests from customers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant