include script for restoring supabase user privileges #45
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A user reported, the following error, when running queries in their Supabase app.
The supabase sdk uses the "postgres" user to perform queries in a schema's table. If
snaplet restore
, is ran without the--no-reset
, the default privileges for this user are dropped and not restored. This may also be true for other users.To restore the privileges, the user should run this script in after restoring with Snaplet.
This is only required for restores, missing the
--no-reset
flag. In the future this flag will automatically be inserted for Supabase users.