Files
supabase/apps/studio/components/interfaces/ConnectSheet/ConnectStepsSection.tsx
Joshen Lim b1b2cf3e6b Update checks for showing ipv4 callout (#51018)
## Context

Updates checks for showing IPv4 add on callouts, should only be visible
if the project's provider is AWS

Involves updating 3 files:
- `ConnectionPooling.tsx` - adds check for cloud provider + enabled
features
- `ConnectStepsSection.tsx` - adds check for cloud provider + enabled
features
- `Ipv4StatusPanel.tsx` - realised this is dead code, so deleted

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Updates**
* IPv4 add-on notices in connection setup and connection pooling appear
only for AWS projects with IPv4 enabled, when the existing connection
and configuration requirements are met.
* **Removals**
* The standalone IPv4 status panel has been removed from the connection
setup flow.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-09-29 20:30:14 +08:00

355 lines
13 KiB
TypeScript

import { useParams } from 'common'
import dynamic from 'next/dynamic'
import Link from 'next/link'
import { useMemo, useRef, type ComponentType } from 'react'
import { Button } from 'ui'
import { Admonition } from 'ui-patterns/Admonition'
import { GenericSkeletonLoader } from 'ui-patterns/ShimmeringLoader'
import type {
ConnectionStringPooler,
ConnectState,
DeploymentMode,
ProjectKeys,
ResolvedStep,
StepContentProps,
} from './Connect.types'
import { ConnectSheetStep } from './ConnectSheetStep'
import {
resolveContentPath,
shouldFetchDataApiConfig,
shouldShowDataApiDisabledWarning,
shouldShowIpv4AddonNotice,
shouldShowSelfHostedMcpNotice,
shouldShowSessionPoolerNotice,
} from './ConnectStepsSection.utils'
import { CopyPromptButton } from './CopyPromptAdmonition'
import { buildConnectionStringPooler, getConnectionStrings } from './DatabaseSettings.utils'
import { getAddons } from '@/components/interfaces/Billing/Subscription/Subscription.utils'
import { DocsButton } from '@/components/ui/DocsButton'
import { InlineLink } from '@/components/ui/InlineLink'
import { useProjectSettingsV2Query } from '@/data/config/project-settings-v2-query'
import { usePgbouncerConfigQuery } from '@/data/database/pgbouncer-config-query'
import { useSupavisorConfigurationQuery } from '@/data/database/supavisor-configuration-query'
import { useProjectAddonsQuery } from '@/data/subscriptions/project-addons-query'
import { useCheckEntitlements } from '@/hooks/misc/useCheckEntitlements'
import { useDeploymentMode } from '@/hooks/misc/useDeploymentMode'
import { useIsDataApiEnabled } from '@/hooks/misc/useIsDataApiEnabled'
import { useIsFeatureEnabled } from '@/hooks/misc/useIsFeatureEnabled'
import { useIsAwsCloudProvider, useIsHighAvailability } from '@/hooks/misc/useSelectedProject'
import { DOCS_URL } from '@/lib/constants'
import { pluckObjectFields } from '@/lib/helpers'
interface ConnectStepsSectionProps {
steps: ResolvedStep[]
state: ConnectState
projectKeys: ProjectKeys
}
/**
* Hook to fetch and prepare connection strings for step content.
*/
function useConnectionStringPooler(deploymentMode: DeploymentMode): ConnectionStringPooler {
const { ref: projectRef } = useParams()
const { hasAccess: allowPgBouncerSelection } = useCheckEntitlements('dedicated_pooler')
const isHighAvailability = useIsHighAvailability()
const { data: settings } = useProjectSettingsV2Query({ projectRef })
// Multigres has no pooler, so the pooler config endpoints don't apply
const { data: pgbouncerConfig } = usePgbouncerConfigQuery(
{ projectRef },
{ enabled: !isHighAvailability }
)
const { data: supavisorConfig } = useSupavisorConfigurationQuery(
{ projectRef },
{ enabled: !isHighAvailability }
)
const { data: addons } = useProjectAddonsQuery({ projectRef })
const { ipv4: ipv4Addon } = getAddons(addons?.selected_addons ?? [])
// Each intermediate derived value is memoized so its reference stays stable
// across renders while the upstream query data is unchanged. Without this,
// pluckObjectFields / getConnectionStrings would mint fresh objects every
// render and invalidate the final useMemo on each tick (and ripple through
// every consumer that lists ConnectionStringPooler in their own deps).
const connectionInfo = useMemo(() => {
const DB_FIELDS = ['db_host', 'db_name', 'db_port', 'db_user', 'inserted_at']
const emptyState = { db_user: '', db_host: '', db_port: '', db_name: '' }
return pluckObjectFields(settings || emptyState, DB_FIELDS)
}, [settings])
const poolingConfigurationShared = supavisorConfig?.find((x) => x.database_type === 'PRIMARY')
const poolingConfigurationDedicated = allowPgBouncerSelection ? pgbouncerConfig : undefined
const connectionStringsShared = useMemo(
() =>
getConnectionStrings({
connectionInfo,
poolingInfo: {
connectionString: poolingConfigurationShared?.connection_string ?? '',
db_host: poolingConfigurationShared?.db_host ?? '',
db_name: poolingConfigurationShared?.db_name ?? '',
db_port: poolingConfigurationShared?.db_port ?? 0,
db_user: poolingConfigurationShared?.db_user ?? '',
},
metadata: { projectRef },
}),
[connectionInfo, poolingConfigurationShared, projectRef]
)
const connectionStringsDedicated = useMemo(
() =>
poolingConfigurationDedicated !== undefined
? getConnectionStrings({
connectionInfo,
poolingInfo: {
connectionString: poolingConfigurationDedicated.connection_string,
db_host: poolingConfigurationDedicated.db_host,
db_name: poolingConfigurationDedicated.db_name,
db_port: poolingConfigurationDedicated.db_port,
db_user: poolingConfigurationDedicated.db_user,
},
metadata: { projectRef },
})
: undefined,
[connectionInfo, poolingConfigurationDedicated, projectRef]
)
return useMemo(
() =>
buildConnectionStringPooler({
deploymentMode,
connectionInfo,
connectionStringsShared,
connectionStringsDedicated,
ipv4Addon: !!ipv4Addon,
isHighAvailability,
}),
[
deploymentMode,
connectionInfo,
connectionStringsShared,
connectionStringsDedicated,
ipv4Addon,
isHighAvailability,
]
)
}
// Vite needs `import.meta.glob` to statically discover the step content
// modules because the `${filePath}` template can span multiple directory
// segments (`flask/supabasepy`, `steps/shadcn/command`, ...) which Vite's
// dynamic-import-vars plugin can't analyze. Skip the glob on the SSR bundle
// — Vite replaces `import.meta.env.SSR` at build time and tree-shakes the
// call so the 37 content modules stay out of the server graph (pulling them
// in reshuffles chunks enough to surface latent circular-dep bugs in
// unrelated modules). Next/webpack doesn't know about `import.meta.glob`
// either; the try/catch lets that branch fall through to the webpack-friendly
// `import()` below.
let contentModules: Record<string, () => Promise<unknown>> = {}
if (!import.meta.env?.SSR) {
try {
contentModules = import.meta.glob('./content/**/content.{tsx,ts}')
} catch {
// webpack build: import.meta.glob is undefined, keep empty map
}
}
type StepContentModule = { default: ComponentType<StepContentProps> }
/**
* Dynamically loads and renders a content component from the content directory.
* All step content uses this unified loader - no built-in component registry needed.
*/
function StepContent({
contentId,
state,
projectKeys,
connectionStringPooler,
deploymentMode,
}: {
contentId: string
state: ConnectState
projectKeys: ProjectKeys
connectionStringPooler: ConnectionStringPooler
deploymentMode: DeploymentMode
}) {
// Resolve any template placeholders in the content path
const filePath = useMemo(() => resolveContentPath(contentId, state), [contentId, state])
// Dynamically import the content component
const ContentComponent = useMemo(() => {
const viteLoader =
contentModules[`./content/${filePath}/content.tsx`] ??
contentModules[`./content/${filePath}/content.ts`]
const loader = viteLoader
? (viteLoader as () => Promise<StepContentModule>)
: () =>
import(/* @vite-ignore */ `./content/${filePath}/content`) as Promise<StepContentModule>
return dynamic<StepContentProps>(loader, {
loading: () => (
<div className="p-4 min-h-[200px]">
<GenericSkeletonLoader />
</div>
),
})
}, [filePath])
return (
<ContentComponent
state={state}
projectKeys={projectKeys}
connectionStringPooler={connectionStringPooler}
deploymentMode={deploymentMode}
/>
)
}
export function ConnectStepsSection({ steps, state, projectKeys }: ConnectStepsSectionProps) {
const { ref } = useParams()
const isAws = useIsAwsCloudProvider()
const stepsContainerRef = useRef<HTMLDivElement | null>(null)
const deploymentMode = useDeploymentMode()
const isHighAvailability = useIsHighAvailability()
const connectionStringPooler = useConnectionStringPooler(deploymentMode)
const { projectAddonsDedicatedIpv4Address } = useIsFeatureEnabled([
'project_addons:dedicated_ipv4_address',
])
const { data: ipv4Addon } = useProjectAddonsQuery(
{ projectRef: ref },
{
select: (data) => {
const selectedAddons = data?.selected_addons ?? []
return selectedAddons.find((addon) => addon.type === 'ipv4')
},
}
)
const showIpv4AddonNotice = shouldShowIpv4AddonNotice({
isAws,
isPlatform: deploymentMode.isPlatform,
isIpv4Enabled: projectAddonsDedicatedIpv4Address,
mode: state.mode,
connectionMethod: state.connectionMethod,
useSharedPooler: state.useSharedPooler,
hasIpv4Addon: !!ipv4Addon,
isHighAvailability,
})
const showSessionPoolerNotice = shouldShowSessionPoolerNotice({
isPlatform: deploymentMode.isPlatform,
mode: state.mode,
connectionMethod: state.connectionMethod,
})
const showSelfHostedMcpNotice = shouldShowSelfHostedMcpNotice({
isSelfHosted: deploymentMode.isSelfHosted,
mode: state.mode,
})
const shouldFetchDataApiStatus = shouldFetchDataApiConfig({
mode: state.mode,
})
const {
isEnabled: isDataApiEnabled,
isPending: isDataApiConfigPending,
isError: isDataApiConfigError,
} = useIsDataApiEnabled({
projectRef: ref,
enabled: shouldFetchDataApiStatus,
})
const showDataApiDisabledWarning = shouldShowDataApiDisabledWarning({
mode: state.mode,
isDataApiEnabled,
isPending: isDataApiConfigPending,
isError: isDataApiConfigError,
})
if (steps.length === 0) return null
return (
<div className="bg-muted/50 flex-1">
<div className="p-8 flex flex-col gap-y-6">
<div className="flex items-center justify-between gap-4">
<h3>Follow these steps</h3>
<CopyPromptButton stepsContainerRef={stepsContainerRef} />
</div>
{showDataApiDisabledWarning && (
<Admonition
type="warning"
layout="responsive"
title="Database access requires the Data API"
description="Client library database queries will not work until the Data API is enabled."
actions={[
<Button asChild key="enable">
<Link href={`/project/${ref}/integrations/data_api`}>Enable Data API</Link>
</Button>,
]}
/>
)}
{showIpv4AddonNotice && (
<Admonition
type="default"
layout="responsive"
title={`${state.connectionMethod === 'direct' ? 'Direct connections use' : 'Transaction pooler uses'} IPv6 by default`}
description={
<>
Enable the dedicated IPv4 address add-on to connect from IPv4-only networks.{' '}
<InlineLink href={`${DOCS_URL}/guides/platform/ipv4-address`}>
Learn more
</InlineLink>
</>
}
actions={
<Button asChild>
<Link href={`/project/${ref}/settings/addons?panel=ipv4`}>Enable IPv4 add-on</Link>
</Button>
}
/>
)}
{showSessionPoolerNotice && (
<Admonition
type="default"
title="Only use session pooler on an IPv4 network"
description="Session pooler connections are IPv4 proxied for free. Use direct connection if connecting via an IPv6 network."
/>
)}
{showSelfHostedMcpNotice && (
<Admonition
type="default"
title="MCP for self-hosted Supabase requires extra setup"
description="The configuration below points at the hosted Supabase MCP server. To use MCP against your self-hosted instance, follow the self-hosted MCP guide."
actions={[
<DocsButton key="docs" href={`${DOCS_URL}/guides/self-hosting/enable-mcp`} />,
]}
/>
)}
<div ref={stepsContainerRef}>
{steps.map((step, index) => (
<ConnectSheetStep
key={step.id}
number={index + 1}
title={step.title}
description={step.description}
optional={step.optional}
>
<StepContent
contentId={step.content}
state={state}
projectKeys={projectKeys}
connectionStringPooler={connectionStringPooler}
deploymentMode={deploymentMode}
/>
</ConnectSheetStep>
))}
</div>
</div>
</div>
)
}