Ability to split metadata yaml into files

Our use case:

• A few hundred tables
• YAML files manually configured/updated on Git
• CI/CD based on git and the cli-migrations-v2 image

The CLI forces us to have all table configuration in a single tables.yaml file that is a few thousand lines long and… a mess.

We would like to be able to something like this:

/metadata
-- table1.yaml
-- table2.yaml
      ...
-- tableN.yaml

Which would allow a much easier (and safer) process of development and review.

This might be somewhat related to https://github.com/hasura/graphql-engine/issues/3545, but I’ve been unable to find a PR for that and the CLI fails if you don’t have a tables.yaml file.

[malkhuzayyim]

@ferm10n just a standard “file per tracked table/view” would be a huge win over having a single yaml file which is in the thousands of lines long. And the switch is pretty straight forward.

It’s true I’m not considering other .yaml files in the metadata, but I’m personally only invested in having the tables file split up. The rest I can live with being in one file as I don’t rely on them that much.

[malkhuzayyim]

@ferm10n If I may chime in.

I think a primary candidate for splitting is the “tables.yaml”, as i imagine it is by far the most used file in hasura for the average use case, as all table info, permissions and events go there.

So the directory structure may stay the same for everything else in a hasura project, just the tables.yaml would become something like:

tables/
- table1.yaml
- table2.yaml
- table3.yaml
...etc

That would be a quick and easy win I believe, its probably very viable to do that while maintaining backwards compatibility too.