In the current review app deployment implementation, before launching a pull request app, any user with the PR app name in the PostgreSQL cluster is first dropped, but what if a user cannot be dropped because it owns some database objects (such as tables, views, functions, etc.)? In this case, these objects need to be reassigned to a reliable user like postgres before dropping the user.
In the current review app deployment implementation, before launching a pull request app, any user with the PR app name in the PostgreSQL cluster is first dropped, but what if a user cannot be dropped because it owns some database objects (such as tables, views, functions, etc.)? In this case, these objects need to be reassigned to a reliable user like
postgresbefore dropping the user.Closes #19