On db migration, migrations files are auto deleted v2.33.1

[JumBay]

Version Information

Server Version: 2.33.1
CLI Version (for CLI related issue):

Environment

Macos 13.5.1 (22G90)

What is the current behaviour?

When I do a migration (modifying my database or adding permission), the migrations files are created and then immediately removed as you can see on the video.

I switched back to hasura 2.27.0 (cli and docker) and I don't have the issue anymore. I add issue on 2.32.1 too

Screenshots or Screencast

Screen.Recording.2023-09-01.at.23.21.08.mov

Please provide any traces or logs that could help here.

Any possible solutions/workarounds you're aware of?

Keywords

[edmundmunday]

This seems to be related to the issue people are experiencing here: https://discord.com/channels/407792526867693568/1146076819301355591

[lazakrisz]

I had a very similar issue with Hasura CLI version 2.32.1 and I have posted my findings in the following issue:#9862 (comment)

Could you please check your metadata status?

What happened in my case is that my metadata status was in an inconsistent state due to trackable functions not being tracked (highlighted in the linked issue) and whenever I did something through the console (created a table, updated a field, made some metadata changes: update an action, event handler etc...) nothing was visible

On the console I started querying the console for my migration status and it kept returning with the following strange migrations:

It had a timestamp but it essentially had a - where the name of the migration should have been, it also was not present on my disk nor in the docker container, only the DB. I suspect this could be due to the fact that the engine was not able to generate the metadata because it was already in an inconsistent state?

[venelin-zek]

For anyone experiencing the issue and thinking how to fix it, you can downgrade the hasura-cli:

hasura update-cli --version 2.32.0

[rikinsk]

Folks, patches for v2.32 and v2.33 have been released with fixes for this. You will just need to update the CLI for the fix.