Document Supabase support for RDI

[ZdravkoDonev-redis]

What changed

• Add a dedicated guide for preparing hosted Supabase PostgreSQL as an RDI source.
• Document the supported hosted Supabase version (PostgreSQL 17).
• Cover direct-endpoint networking, IPv4 requirements, network restrictions, replication-role permissions, RLS, publications, TLS, self-managed RDI configuration, Redis Cloud setup, replication-slot monitoring, and major-version upgrades.
• Clarify that Supabase AWS PrivateLink uses an unsupported AWS RAM Resource Configuration/Resource endpoint flow.
• Remove the obsolete PostgreSQL-page note that said hosted Supabase was unsupported.

Why

RDI 1.19.0 was qualified against hosted Supabase PostgreSQL 17.6 through both self-managed RDI and Redis Cloud RDI. Snapshot, insert/update/delete CDC, TLS, public connectivity, network restrictions, cross-account secret access, and stop/start WAL catch-up were validated. Customers need a supported setup path and clear boundaries.

User impact

Customers can configure Supabase as a PostgreSQL source using the public direct endpoint and understand the required privileges and networking. The guide explicitly distinguishes supported public connectivity from the currently unsupported Supabase PrivateLink architecture.

Validation

• git diff --cached --check
• Hugo 0.143.1 full build: passed (18,137 pages)
• Rendered the new Supabase page and verified its key sections and internal references

The build emitted two pre-existing REF_NOT_FOUND warnings from content/operate/rs/8.0/flex/_index.md; neither is related to this change.

[github-actions]

🧠 Redis Memory

Found 5 related items from repository history:

• PR — DOC-5868 RDI: add Supabase to list of supported source databases

  PostgreSQL setup instructions apply since Supabase uses PostgreSQL internally.

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• PR — DOC-6475 updated RDI supported sources

  This is the latest info for Debezium 3.4. Let me know if the AWS/GCP product versions also need to be updat

• Commit — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  DOC-6878 Expand RDI FAQ CDC section with all supported databases

• PR — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  What

Memory updated at ec993a2

[github-actions]

Staging links:
https://redis.io/docs/staging/agent/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/postgresql/
https://redis.io/docs/staging/agent/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/supabase/
https://redis.io/docs/staging/agent/rdi-supabase/integrate/redis-data-integration/
https://redis.io/docs/staging/agent/rdi-supabase/integrate/redis-data-integration/architecture/
https://redis.io/docs/staging/agent/rdi-supabase/integrate/redis-data-integration/data-pipelines/prepare-dbs/
https://redis.io/docs/staging/agent/rdi-supabase/integrate/redis-data-integration/installation/reqsummary

[github-actions]

🧠 Redis Memory

Found 5 related items from repository history:

• Commit — Document Supabase support for RDI

  Document Supabase support for RDI

• PR — DOC-5868 RDI: add Supabase to list of supported source databases

  PostgreSQL setup instructions apply since Supabase uses PostgreSQL internally.

• PR — DOC-6833: Fix four RDI Cloud doc issues from #rdi-cloud

  • Remove Active-Active from the 'multiple targets' use case sentence; add it as an explicit unsupported target topology under 'When not to u

• PR — DOC-6475 updated RDI supported sources

  This is the latest info for Debezium 3.4. Let me know if the AWS/GCP product versions also need to be updat

• Commit — DOC-6878 Expand RDI FAQ CDC section with all supported databases

  DOC-6878 Expand RDI FAQ CDC section with all supported databases

Memory updated at bda2488