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-3548] Move WritableManifest to dbt/artifacts #9378

Closed
1 task done
Tracked by #9099
MichelleArk opened this issue Jan 16, 2024 · 0 comments · Fixed by #9377
Closed
1 task done
Tracked by #9099

[CT-3548] Move WritableManifest to dbt/artifacts #9378

MichelleArk opened this issue Jan 16, 2024 · 0 comments · Fixed by #9377
Assignees

Comments

@MichelleArk
Copy link
Contributor

MichelleArk commented Jan 16, 2024

Housekeeping

  • I am a maintainer of dbt-core

Short description

As part of an effort to move any ArtifactMixin subclasses upstream of other core modules into the top -level dbt/artifacts directory, we need to move WritableManifest. This will pull in many other dependencies - notably contracts.graph.nodes.

This ticket is just to get the initial WritableArtifact in dbt/artifacts without moving all the upstream dependencies to get the foundation set.

Acceptance criteria

A spike report that highlights any potential approaches and their tradeoffs, as well as a summary of any potential blockers encountered.

Impact to Other Teams

N/A - should be a refactor.

@github-actions github-actions bot changed the title Move WritableManifest to dbt/artifacts [CT-3548] Move WritableManifest to dbt/artifacts Jan 16, 2024
@MichelleArk MichelleArk changed the title [CT-3548] Move WritableManifest to dbt/artifacts [CT-3548] Move WritableManifest to dbt/artifacts [spike+] Jan 16, 2024
@MichelleArk MichelleArk self-assigned this Jan 16, 2024
@MichelleArk MichelleArk changed the title [CT-3548] Move WritableManifest to dbt/artifacts [spike+] [CT-3548] Move WritableManifest to dbt/artifacts Jan 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant