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

Migrate to using Mergeable from `dbt-common #9505

Closed
1 task done
QMalcolm opened this issue Feb 1, 2024 · 0 comments · Fixed by #9509
Closed
1 task done

Migrate to using Mergeable from `dbt-common #9505

QMalcolm opened this issue Feb 1, 2024 · 0 comments · Fixed by #9509
Assignees
Labels
user docs [docs.getdbt.com] Needs better documentation

Comments

@QMalcolm
Copy link
Contributor

QMalcolm commented Feb 1, 2024

Housekeeping

  • I am a maintainer of dbt-core

Short description

We're currently in the process of moving the "data resource" portion on nodes to dbt/artifacts. Some of those artifacts depend on Mergeable which has been defined on core. In order to move the data resources to dbt/artifacts, we thus need to move Mergeable upstream of core. We moved Mergeable to dbt-common in dbt-labs/dbt-common#59, and released this change in dbt-common 0.1.3. As such as, in order to unblock some of the dbt/artifacts migration work, we first need to update references to Mergeable in core to use the dbt-common definition.

Acceptance criteria

All uses of Mergeable in core use the definition in dbt-common

Suggested Tests

None

Impact to Other Teams

None

Will backports be required?

No

Context

No response

@QMalcolm QMalcolm added the user docs [docs.getdbt.com] Needs better documentation label Feb 1, 2024
@QMalcolm QMalcolm self-assigned this Feb 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
user docs [docs.getdbt.com] Needs better documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant