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: recreate DB on schema change #4697

Merged
merged 4 commits into from
Mar 6, 2025

Conversation

stuartwdouglas
Copy link
Collaborator

No description provided.

This was referenced Feb 27, 2025
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/recreate-on-schema-change branch 2 times, most recently from fdd374b to 6b651e8 Compare March 6, 2025 03:06
@stuartwdouglas stuartwdouglas changed the title wip: recreate DB on schema change feat: recreate DB on schema change Mar 6, 2025
@stuartwdouglas stuartwdouglas marked this pull request as ready for review March 6, 2025 03:07
@stuartwdouglas stuartwdouglas requested review from alecthomas and a team as code owners March 6, 2025 03:07
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/recreate-on-schema-change branch from 6b651e8 to 2a4c9d2 Compare March 6, 2025 03:07
Config: &Database{Type: d.Type, Metadata: []Metadata{migration}},
Kind: ResourceTypeSQLMigration,
Config: &Database{Type: d.Type, Metadata: []Metadata{migration}},
DeploymentSpecific: true,
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This means that provision will always be called, even when databases are the same. I'm not sure what impact this would have for the other DB provisioners.

@stuartwdouglas stuartwdouglas requested a review from a team as a code owner March 6, 2025 06:18
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/recreate-on-schema-change branch 2 times, most recently from e526814 to a7c3e48 Compare March 6, 2025 06:27
@stuartwdouglas stuartwdouglas enabled auto-merge (squash) March 6, 2025 06:28
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/recreate-on-schema-change branch 2 times, most recently from 6d2f509 to bb169c6 Compare March 6, 2025 07:57
# Conflicts:
#	backend/provisioner/dev_provisioner.go
@stuartwdouglas stuartwdouglas force-pushed the stuartwdouglas/recreate-on-schema-change branch from bb169c6 to f7a2e12 Compare March 6, 2025 23:20
@stuartwdouglas stuartwdouglas merged commit 95fae2d into main Mar 6, 2025
68 checks passed
@stuartwdouglas stuartwdouglas deleted the stuartwdouglas/recreate-on-schema-change branch March 6, 2025 23:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants