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

[Investigation] Explore options for providing upgrade or migration paths (for snapshots) #10325

Closed
Tracked by #10151
gshank opened this issue Jun 18, 2024 · 1 comment
Assignees
Labels
snapshots Issues related to dbt's snapshot functionality

Comments

@gshank
Copy link
Contributor

gshank commented Jun 18, 2024

Description

As we attempt to make additional features backward compatible, there will be situations (several currently known in the snapshot initiative) where we will want users to run upgrade or migration scripts. These may consist of altering tables or modifying other files.

We should think through how we can provide this functionality in a way that works well for both dbt Core OSS and dbt Cloud users.

Acceptance Criteria

We've identified the path forward and can create tickets to implement the necessary infrastructure.

@gshank gshank added the snapshots Issues related to dbt's snapshot functionality label Jun 18, 2024
@graciegoheen
Copy link
Contributor

graciegoheen commented Jul 15, 2024

investigation

  • throw warning in CI if config has changed
    • could upgrade these to errors WARN_ERROR_OPTIONS
  • provide package with macros to run via run-operation for common migrations
  • rely on user to handle migration however they want to (create a new snapshot, run migration script, etc.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
snapshots Issues related to dbt's snapshot functionality
Projects
None yet
Development

No branches or pull requests

2 participants