[hasura cloud] Inconsistencies when applying metadata after table rename

Using a local hasura UI, we did rename one of our table - operation resulting in a migration file. That table was used in an event trigger insert, but the trigger was not renamed automatically by hasura, so we did keep the event trigger name. We tested successfully several times this on our local machines the metadata apply. But when trying to apply the metadata in hasura cloud, we did get inconsistencies for the event trigger name:

level=fatal msg="failed to apply metadata: cannot apply metadata on the database: [unexpected] cannot continue due to inconsistent metadata ($.args)\r\n\nreason: table \"<old_table_name>\" does not exist type: event_trigger

After multiple unsuccessful tries to resolve the inconsistencies on hasura cloud, we did rename the trigger and this solved the problem.

We consider this a bug since the event triggers have names that we do assign manually.

[maria-nemeti]

@codingkarthik The cloud instance is not running on an empty DB, but on an already populated DB with data in table A and event triggers defined.

[codingkarthik]

Hello @maria-nemeti

Unfortunately, I’m still not able to reproduce this issue. Can you try reproducing this issue on a local instance which is a replica of the cloud instance? I would like to know if the issue is cloud specific.