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

[CT-2325] Validate public models are not materialized as ephemeral #7226

Closed
Tracked by #7372 ...
MichelleArk opened this issue Mar 27, 2023 · 0 comments · Fixed by #7794
Closed
Tracked by #7372 ...

[CT-2325] Validate public models are not materialized as ephemeral #7226

MichelleArk opened this issue Mar 27, 2023 · 0 comments · Fixed by #7794
Assignees
Labels
model_groups_access Issues related to groups multi_project

Comments

@MichelleArk
Copy link
Contributor

Ephemeral materializations shouldn't be made public because there is no database identifier that gets materialized in the data warehouse for use as a 'production pointer' by downstream dbt projects.

This could be a parse-time error (similar to what's been proposed for #7063 (comment)), or optionally could be a warning surfaced prior to writing a publication artifact that excludes any public models with ephemeral materializations. Either way, public models with ephemeral materializations should not be included as part of the publication artifact because there will be no way to resolve the reference from a downstream project.

@github-actions github-actions bot changed the title Prevent publication of public models with ephemeral materialization [CT-2325] Prevent publication of public models with ephemeral materialization Mar 27, 2023
@MichelleArk MichelleArk changed the title [CT-2325] Prevent publication of public models with ephemeral materialization [CT-2325] Validate public models are not materialized as ephemeral May 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
model_groups_access Issues related to groups multi_project
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant