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

Update yml vars for running in same project #985

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ciansnowplow
Copy link
Contributor

I have added the snowplow__user_mapping_source: "{{ ref('snowplow_unified_user_mapping') }}" to the yml vars for running the attribution in the same project as unified. This is required for the model to run successfully. I have also updated a broken link to the unified package.

I have added the snowplow__user_mapping_source: "{{ ref('snowplow_unified_user_mapping') }}" to the yml vars for running the attribution in the same project as unified. This is required for the model to run successfully. I have also updated a broken link to the unified package.
Copy link

netlify bot commented Aug 21, 2024

Deploy Preview for snowplow-docs ready!

Name Link
🔨 Latest commit 1a7d0d5
🔍 Latest deploy log https://app.netlify.com/sites/snowplow-docs/deploys/66c60404f913010008b00fea
😎 Deploy Preview https://deploy-preview-985--snowplow-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@johnmicahreid johnmicahreid requested review from agnessnowplow and ilias1111 and removed request for agnessnowplow October 30, 2024 09:33
Copy link
Contributor

@agnessnowplow agnessnowplow left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the changes! The link is still broken and upon checking it a bit it seems links are not rendered correctly inside the details tag so I'd suggest to remove it, simply because it is not too vital to be there anyway.

@@ -96,11 +96,12 @@ Your channel and spend data will be summed separately in the `attribution_overvi

<details>
<summary>Running both Unified and Attribution dbt packages from the same project</summary>
Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the [Unified Digital](/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-models/dbt-unified-data-model/index.md) and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables:
Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the [Unified Digital](/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-models/dbt-unified-data-model/) and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the [Unified Digital](/docs/modeling-your-data/modeling-your-data-with-dbt/dbt-models/dbt-unified-data-model/) and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables:
Although auto-deployed packages managed via Console run in separate projects, for others there may be use cases when it is more practical to run both the Unified Digital and Attribution dbt packages from the same project. We purposefully did not directly link the two packages and this method of running is non-standard but there is a way to make it work. When specifying the sources just make sure you change the default source references to: ref('') instead of hard coding the schema.table_name for these variables:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants