When executing a permissions change in the hasura console with migrations enabled, the up migration is correct and drops the existing permission and creates the new one

- args:
    role: user
    table:
      name: table_name
      schema: public
  type: drop_insert_permission
- args:
    permission:
    role: user
       ---- new permissions here
    table:
      name: table_name
      schema: public
  type: create_insert_permission

However the down migration is incorrect, it appears to reverse the create_insert_permission and drop_insert_permission from above. It should rather do drop_insert_permission then a create_insert_permission with the original permissions before the change was made.

It's not a problem for my project as I don't use the auto-generated migrations but thought I should raise as if someone relies on this for their down migrations then they could end up with permissions different to how they expected.