hasura 2.0.3 and dipdup 2.0.6 don't work about dipdup HOT 5 CLOSED

Hasura error when schema_name is undefined

from dipdup.

@bb4L, @sbihel, fixed in 2.0.7, Docker images will be available soon.

A small feature (probably no one knew about it except me) was removed in this release. Before today, DipDup tried to merge existing Hasura metadata: tables, queries and REST endpoints. This allowed to use a single Hasura deployment with multiple DipDup instances. Could save some time developing multiple backends at once. However, the following problems revealed:

• It's hard to get underlying database schema with Hasura introspection queries
• Orphaned entities must be tracked
• Code complexity grows as edge cases are discovered

So I decided to remove corresponding code and reset Hasura metadata on every configuration. Please reply in this thread or Baking Bad chats if you'd like to have an ability to inject arbitrary metadata (in addition to queries from project/graphql directory) on Hasura configuration.

from dipdup.

@droserasprout
i updated to dipdup 2.0.7 and hasura 2.0.3 now i get: Unknown table `hat` ( same for dipdup 2.0.7 and hasura 2.0.6)

am i missing something? / some configurations?

EDIT:
not sure if related but if i'm not mistaking i just had the issue when restarting from "scratch" with dipdup 2.0.5 and hasura 1.3.3 it doesn't automatically expose the tables on hasura

from dipdup.

@bb4L, please post here or PM me code of models.py module of your project, so I can reproduce this issue.

from dipdup.

Fixed in 2.0.8.

from dipdup.