hasura / hasura/graphql-engine
Hasura Console Fails to Produce Migration Files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 32.1k
- Forks
- 3k
- PR merge metrics
- PR metrics pending
Description
Version Information
Server Version:
CLI Version (for CLI related issue): version=v2.14.0-cloud.1
What is the current behaviour?
Sometimes when running sql commands with "This is a migration" checkbox console fails to produce the migration files.
What is the expected behaviour?
Create the the migration files properly.
How to reproduce the issue?
- I have seen this a lot immediately after updating the CLI
Any possible solutions/workarounds you're aware of?
When I restart the console it usually resolves itself.
Revert any change, restart the console, and reapply the changes.
However, sometimes you can't revert the changes for example adding enum values so I have to resort to dropping the entire enum and readding it which is cumbersome.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the failure in Hasura Console after updating CLI version v2.14.0-cloud.1, using SQL commands with the "This is a migration" checkbox and checking whether migration files are produced. Compare behavior after restarting the console, including changes such as adding enum values; done means the migration files are consistently created without requiring a restart or destructive workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, typescript
- Domain
- database, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100