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-2590] Switch publication artifact from file to structured log #7685

Closed
Tracked by #7372
jtcohen6 opened this issue May 23, 2023 · 0 comments · Fixed by #7686
Closed
Tracked by #7372

[CT-2590] Switch publication artifact from file to structured log #7685

jtcohen6 opened this issue May 23, 2023 · 0 comments · Fixed by #7686
Assignees
Labels
multi_project tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality

Comments

@jtcohen6
Copy link
Contributor

As described in #7469 and implemented in #7656, dbtRunner will accept publication artifacts as programmatic input.

Let's switch from writing/reading publication artifacts to/from the file system, in favor of only supporting a structured event/log output and a programmatic input. Among other reasons, this will:

  • better align with our intention for deploying as a service in dbt Cloud
  • enable us to make implementation changes in the future, without having committed to a contracted interface in v1.6
@jtcohen6 jtcohen6 added tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality multi_project labels May 23, 2023
@github-actions github-actions bot changed the title Switch publication artifact from file to structured log [CT-2590] Switch publication artifact from file to structured log May 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
multi_project tech_debt Behind-the-scenes changes, with little direct impact on end-user functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants