Fix issue of RLS not working with Postgrest and Storage #560
+45
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## develop #560 +/- ##
===========================================
- Coverage 79.39% 72.34% -7.06%
===========================================
Files 9 9
Lines 165 188 +23
===========================================
+ Hits 131 136 +5
- Misses 34 52 +18
☔ View full report in Codecov by Sentry. |
silentworks
changed the title
This was referenced Sep 26, 2023
|
@silentworks Much appreciated!! |
This was referenced Sep 27, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What kind of change does this PR introduce?
This will now allow the correct auth headers for a authenticated user to be passed over to the postgrest client. In this setup the postgrest and storage client are lazy initialised and each time a event triggers that could cause an auth token to update we reset the private variable holding the postgrest and storage clients.
What is the current behavior?
No complying with the RLS policies without handling it in your code yourself
What is the new behavior?
Automatic handling of complying with the RLS polices with postgrest and storage.
Additional context
Fixes #185