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

[feat] Setup task expansion to cover lifecycle of dbt-coves vendored components #323

Open
z3z1ma opened this issue Feb 15, 2023 · 0 comments
Labels
enhancement New feature or request triaged: yes Has been approved for future implementation

Comments

@z3z1ma
Copy link
Contributor

z3z1ma commented Feb 15, 2023

Is your feature request related to a problem? Please describe.

dbt-coves can set up github actions, airflow, and other pieces of the data stack in a pre-configured simple way.

dbt-coves setup macros # use dbt-package
dbt-coves update macros # use a version matrix and update packages.yml for the user

These are all things we can "setup" for the user but require ongoing lifecycle management.

dbt-coves setup github-actions
dbt-coves setup --update github-actions

dbt-coves setup airflow
dbt-coves setup --update airflow

dbt-coves setup permifrost
dbt-coves setup --update permifrost

dbt-coves setup training-and-tools
dbt-coves setup --update training-and-tools

dbt-coves setup snowpark
dbt-coves setup --update snowpark

Managing the lifecycle of files in user owned repos involves change management. Copier enables efficient change management (including handling merge conflicts) and leverages a centralized repository of templates which provide the actual content. Furthermore by wrapping in dbt-coves setup, we will be able to provide a changelog to assist users in updating dbt-coves derived components in their data stack codebase. We can also consider a dbt-coves setup --update --all [--dry-run ?] command which checks for component updates and outputs actions / changelogs to terminal.

image

@z3z1ma z3z1ma self-assigned this Feb 15, 2023
@z3z1ma z3z1ma added the enhancement New feature or request label Feb 15, 2023
@github-actions github-actions bot added the triaged: no Hasn't been approved for future implementation label Feb 15, 2023
@z3z1ma z3z1ma removed the triaged: no Hasn't been approved for future implementation label Feb 16, 2023
@BAntonellini BAntonellini added the triaged: yes Has been approved for future implementation label Jun 6, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request triaged: yes Has been approved for future implementation
Projects
None yet
Development

No branches or pull requests

2 participants