add options to create migration from files from sql and server (close #1699) #1761
Conversation
This file contains hidden or 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
Contributor
|
Review app for commit 17b238c deployed to Heroku: https://hge-ci-pull-1761.herokuapp.com |
shahidhk
requested changes
Mar 18, 2019
|
Deploy preview for hasura-docs ready! Built with commit 657a257 |
shahidhk
requested changes
Mar 18, 2019
Contributor
|
Review app for commit e67ee51 deployed to Heroku: https://hge-ci-pull-1761.herokuapp.com |
shahidhk
approved these changes
Mar 18, 2019
Contributor
|
Review app for commit 657a257 deployed to Heroku: https://hge-ci-pull-1761.herokuapp.com |
Contributor
|
Review app https://hge-ci-pull-1761.herokuapp.com is deleted |
hasura-bot
pushed a commit
that referenced
this pull request
Mar 26, 2025
<!-- The PR description should answer 2 important questions: --> ### What The goal here is to make DDN easier to deploy and manage, so that artifacts don't need to be rebuilt and MBS doesn't need to be deployed in lock-step with engine. Once we have confidence in this we can start ripping out things from MBS. Maybe it can disappear entirely. Context: https://hasurahq.slack.com/archives/C02G2M3C1T3/p1741734025080149?thread_ts=1740509463.160639&cid=C02G2M3C1T3 <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> ### How <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 619ff8f2060819956260257b1359bc49b4978ee2
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
Something like hasura migrate create --sql-file --metadata-from-server which will create the migration
hasura migrate apply --version xxx --dry-run will add this migration as applied.
Affected components
Related Issues
#1699
Solution and Design
Steps to test and verify
Run
hasura migrate create --sql-file test.sql --metadata-from-server http://localhost:8080The above command will create the migrations under migrations directory.
Now, Run
hasura migrate apply --version <version-of-the-migration> --dry-runThis will mark that version as applied in the database.