chore: create separate staging_ and production_ columns in team_integrations for Power Automate File API keys
#3061
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
|
🤖 Hasura Change Summary compared a subset of table metadata including permissions: Updated Tables (1)
|
DafyddLlyr
approved these changes
Apr 26, 2024
|
Removed vultr server and associated DNS entries |
jessicamcinchak
deleted the
jess/db-migrate-prod-staging-powerautomate-cols
branch
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.
Follows on from theopensystemslab/planx-core#360
I'm updating our data sync script in the same PR here so pizza content will be empty (these cols don't exist on prod yet), but new migration should succeed as expected.