refactor: decouple AuthManager from pg_catalog #263
Closed
+73
−17
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.
Fixes #191
This change decouples AuthManager from PgCatalogContextProvider to unblock issue #189 (moving pg_catalog to a separate module).
Changes:
The architecture now looks like:
AuthManager -> RoleProvider trait RoleProviderBridge -> PgCatalogContextProvider trait pg_catalog uses PgCatalogContextProvider for pg_roles table
This keeps auth concerns separate from pg_catalog while still allowing role information to flow to the pg_roles table.