In some instances of an invalid migrations file hasura-cli does not error, rather it silently ignores the file.

Steps to repro.

Create migrations file 1.up.yaml with this content (with the invalid THIS IS A TEST)

THIS IS A TEST

-   args:
        sql: CREATE TABLE "public"."test"("id" uuid NOT NULL UNIQUE, PRIMARY KEY ("id") );
    type: run_sql
-   args:
        name: test
        schema: public
    type: add_existing_table_or_view

Run hasura migrate status

Output seen:

VERSION  SOURCE STATUS  DATABASE STATUS

Expected output: Some sort of error indicating there is an problem in 1.up.yaml