chore: add new staging team_integrations columns to data sync script
#3042
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
4 tasks
|
Removed vultr server and associated DNS entries |
|
Very open to ideas here - it's currently pretty awkward to do handle this multi step process of adding db columns, and then correctly synching them down. I think your approach of just adding db columns in one PR, resolving quickly with queued up sync script PR, and then actually using those columns is the best approach so far! |
Merged
DafyddLlyr
approved these changes
Apr 23, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A bit of tricky sequencing with this one - Hasura should be healthy, but expect pizza db to be empty with following error because these columns aren't merged to production yet!
Can be safely merged later after #3040 !