Supavisor brings down infrastructure after role modification about supavisor

[saltcod]

Thanks @kdaniel21! Going to transfer this one to the supavisor repo.

[kdaniel21]

@saltcod I'm sorry then for opening it in the repo! My way of thinking was that the bug has (seemingly) already been addressed/fixed in Supavisor, there is just simply no way to interact with the provided API through the Supabase dashboard. That's why I assumed that the Supabase repo is the most appropriate.

[kdaniel21]

Hi, is there any known workarounds to at least recover from this state? This has been affecting us ever since, and I'm still concerned that it will once reach our production environment, leaving us with nothing but waiting that it will recover sometime.

[d-e-h-i-o]

This also happened after this statement:

create user mapping for example_role
server app_db
options (user 'example', password 'wrong_password')

The 'example' user does exist, but the password is wrong.

This bug is quite concerning to use, since it has the potential to bring down production, with no clear path to recovery.