Why do automated Hasura migrations output a metadata.yaml file?

Viewed 191

I am using the console to generate migrations. In addition to the generated migrations, Hasura also writes a metadata.yaml file next to the migration folders:

- config.yaml
- migrations/
    |-- 1583186121964_init/
    |-- 1583363878794_another_migration/
    |-- metadata.yaml  <-- This file is generated along with new migrations,
                           but seems redundant

This seems to be the latest version of the metadata. However, this file does not seem necessary. I can wipe my Hasura state—both PostgresSQL and Hasura—remove this file, and upon hasura migrate apply everything is correctly restored based on the migrations alone. What is this file for? Just in case the migrations are bad?

0 Answers
Related