Add self-hosted Supabase support for local development #1239
+27
−6
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.
📥 Pull Request
📘 Description
This PR adds support for self-hosted Supabase instances in local development environments. The changes enable AgentOps to connect to local Supabase Docker deployments without SSL certificates and handle JWT token differences between hosted and self-hosted Supabase.
Key Changes:
iss(issuer) field optional inSupabaseUserDatamodel since local Supabase doesn't include it in JWT tokensSUPABASE_SSLMODEenvironment variable support with PostgreSQL connection string updatescompose.yamlfor direct database accessSUPABASE_SSLMODEconfiguration option (defaults toprefer)🧪 Testing
issfield)sslmode=disablefor local development🔍 Review Focus Areas
Security Considerations:
issfield optional - ensure this doesn't weaken authentication securitySUPABASE_SSLMODE=disableis only used for local development, not productionCompatibility:
Link to Devin run: https://app.devin.ai/sessions/35e0a46063c744bdb9e75bf5d781c749
Requested by: @areibman