docs: list Postgres/Redis region availability per cloud - #424
Conversation
AWS (RDS/ElastiCache) and GCP (Cloud SQL/Memorystore) ship these services to essentially every region, but Azure Database for PostgreSQL and Azure Managed Redis roll out region-by-region, and the VM SKU Defang picks can still hit regional capacity limits even where the service itself is available. Point readers at the live Azure "Products available by region" page instead of a static list that would go stale. Fixes #423
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Essentials Run ID: 📒 Files selected for processing (5)
Included review availability: 0 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 1 review per hour. 📝 WalkthroughWalkthroughThe documentation now describes regional availability for managed Postgres and Managed Redis across AWS, Azure, and GCP, including Azure location selection guidance. ChangesRegional availability guidance
Priority: ⬇️ Low — Defer this documentation update because it adds regional availability guidance without changing product behavior. Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to The documentation-only regional availability guidance is ready to merge with no established blocking risk. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
Comment |
Summary
Fixes #423 — documents managed Postgres/Redis region availability per cloud, without hardcoding a region list that would go stale.
docs/providers/aws.md): Amazon RDS and ElastiCache ship to every AWS Region launch — one-line note, no gap to document.docs/providers/gcp.md): Cloud SQL and Memorystore for Redis are available in essentially all GCP regions — one-line note with links to the region lists.docs/providers/azure.md): this is the actual gap. Azure Database for PostgreSQL and Azure Managed Redis roll out region-by-region, and Microsoft's own docs point to a live "Products available by region" page rather than a static list, since it changes as regions come online. Also called out: Defang auto-selects a specific VM SKU per tier, which can hit a regional capacity limit even in a region where the service itself is generally available.docs/concepts/managed-storage/managed-postgres.mdxandmanaged-redis.md: short pointer from the "Current Support" table to the new Azure section, instead of duplicating content across pages.Why no static region table
Azure's own docs explicitly say availability is "continually expanding" and defer to a live, filterable page — a static markdown table here would be wrong within weeks. Linking to the authoritative source is more maintainable and avoids a documentation drift risk.
Test plan
npm install+ cloned siblingdefang/samplesrepos +bash scripts/prebuild.sh+npx docusaurus build— build succeeds./docs/providers/azure#managed-postgres-and-redis-region-availability) resolves — it does not appear in the build's "broken anchors" list (which only lists pre-existing unrelated ones).🤖 Generated with Claude Code
Summary by CodeRabbit