Supabase config management update #2
Merged
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.
This pull request refactors the Supabase integration to improve configuration management and standardize module imports. The most important changes include switching from Django settings to environment variables for configuration, updating the environment variable usage in the Supabase initialization function, and restructuring import paths for better modularity.
Configuration Management Updates:
settings) with environment variables (os.getenv) for Supabase configuration inSupabaseService(_service.py). Updated error messages to reflect the new source of configuration.initialize_supabasefunction to prioritize theSUPABASE_SERVICE_ROLE_KEYoverSUPABASE_ANON_KEYfor backend operations, ensuring compatibility with role-based access control. Updated error handling to account for this change. (init.py) [1] [2]Codebase Restructuring:
app.core.third_party_integrations. (tests/conftest.py,tests/test_edge_functions.py,tests/test_integration.py,tests/test_service.py) [1] [2] [3] [4]init.pyto align with the updated project structure.