[v2.0.0-alpha.7] Hasura CLI can't generate migration SQL & track newly created tables on non-default schema

[peteygao]

Hasura CLI version: v2.0.0-alpha.7
Hasura Server version: v2.0.0-cloud.2

Issue Description

When creating a new table via hasura console running against Hasura's cloud instance, creating a new table on a non-default (a.k.a. not public) schema will give an error postgres-error: no schema has been selected to create in. However, the table does get created in the underlying DB. Hasura CLI will not auto-generate a migration SQL nor track it.

However, the same issue DOES NOT occur when creating a new table via the cloud.hasura.io console (it could be because Hasura's cloud console does not generate a migration file?).

The problem appears to be with the way Hasura CLI is trying to generate the SQL migration file, and it's failing that step for tables created on non-default schema.

[scriptonist]

@peteygao I couldn't reproduce this. can you verify if this is still the case?

[rikinsk]

@peteygao I am closing this issue for now as we were not able to reproduce this. Feel free to reopen this in case you are still facing this problem.