mirror of
https://github.com/supabase/supabase.git
synced 2026-10-10 11:55:05 +03:00
## What kind of change does this PR introduce? Mechanical cleanup on top of the Button default-variant change (#50160). ## What is the current behavior? Many callsites still pass `variant="default"` even though that is now the component default. ## What is the new behavior? Removes redundant static `variant="default"` from legacy `Button` and `ButtonTooltip` callsites. Keeps explicit defaults where they document the API: - `button-default.tsx` and `button-sizes.tsx` demos - `DocsButton`, which pins neutral styling at the wrapper boundary ## To test Studio: - [Auth → Rate Limits](https://studio-staging-2s957kwc4-supabase.vercel.app/dashboard/project/_/auth/rate-limits): dirty the form so Cancel appears; Cancel stays neutral, Save stays green - [Project Settings → API Keys](https://studio-staging-2s957kwc4-supabase.vercel.app/dashboard/project/_/settings/api-keys): `DocsButton` in the header actions stays neutral Design system: - [Design system → Button](https://design-system-git-dnywh-dc924ac1-supabase.vercel.app/design-system/docs/components/button): `button-default` / `button-sizes` still show explicit default styling; Primary (green) is restricted to the Primary section (and `asChild`) WWW: - [www → Brand assets](https://zone-www-dot-com-git-dnywh-dc924ac1-supabase.vercel.app/brand-assets): Download logo kit / Download button kit stay neutral
180 lines
6.8 KiB
TypeScript
180 lines
6.8 KiB
TypeScript
import { useParams } from 'common'
|
|
import Link from 'next/link'
|
|
import { useRouter } from 'next/router'
|
|
import { useState } from 'react'
|
|
import {
|
|
Alert,
|
|
AlertDescription,
|
|
AlertDialog,
|
|
AlertDialogAction,
|
|
AlertDialogCancel,
|
|
AlertDialogContent,
|
|
AlertDialogDescription,
|
|
AlertDialogFooter,
|
|
AlertDialogHeader,
|
|
AlertDialogTitle,
|
|
AlertTitle,
|
|
Button,
|
|
DialogSection,
|
|
DialogSectionSeparator,
|
|
WarningIcon,
|
|
} from 'ui'
|
|
|
|
import { BackupsEmpty } from '../BackupsEmpty'
|
|
import { BackupsStorageAlert } from '../BackupsStorageAlert'
|
|
import type { Timezone } from './PITR.types'
|
|
import { getClientTimezone } from './PITR.utils'
|
|
import { PITRForm } from './PITRForm'
|
|
import PITRStatus from './PITRStatus'
|
|
import { FormHeader } from '@/components/ui/Forms/FormHeader'
|
|
import { useBackupsQuery } from '@/data/database/backups-query'
|
|
import { usePitrRestoreMutation } from '@/data/database/pitr-restore-mutation'
|
|
import { useSetProjectStatus } from '@/data/projects/project-detail-query'
|
|
import { useReadReplicasQuery } from '@/data/read-replicas/replicas-query'
|
|
import { PROJECT_STATUS } from '@/lib/constants'
|
|
|
|
export const PITRSelection = () => {
|
|
const router = useRouter()
|
|
const { ref } = useParams()
|
|
|
|
const { data: backups } = useBackupsQuery({ projectRef: ref })
|
|
const { data: databases } = useReadReplicasQuery({ projectRef: ref })
|
|
const { setProjectStatus } = useSetProjectStatus()
|
|
|
|
const [showConfiguration, setShowConfiguration] = useState(false)
|
|
const [showConfirmation, setShowConfirmation] = useState(false)
|
|
const [selectedTimezone, setSelectedTimezone] = useState<Timezone>(getClientTimezone())
|
|
const [selectedRecoveryPoint, setSelectedRecoveryPoint] = useState<{
|
|
selectedTimezone: Timezone
|
|
recoveryTimeTargetUnix: number
|
|
recoveryTimeString: string
|
|
recoveryTimeStringUtc: string
|
|
}>()
|
|
|
|
const hasReadReplicas = (databases ?? []).length > 1
|
|
|
|
const { mutateAsync: restoreFromPitr } = usePitrRestoreMutation({
|
|
onSuccess: (_, variables) => {
|
|
setTimeout(() => {
|
|
setShowConfirmation(false)
|
|
setProjectStatus({ ref: variables.ref, status: PROJECT_STATUS.RESTORING })
|
|
router.push(`/project/${variables.ref}`)
|
|
}, 3000)
|
|
},
|
|
})
|
|
|
|
const { earliestPhysicalBackupDateUnix, latestPhysicalBackupDateUnix } =
|
|
backups?.physicalBackupData ?? {}
|
|
const hasNoBackupsAvailable = !earliestPhysicalBackupDateUnix || !latestPhysicalBackupDateUnix
|
|
|
|
const onConfirmRestore = async () => {
|
|
if (!ref) return console.error('Project ref is required')
|
|
if (!selectedRecoveryPoint?.recoveryTimeTargetUnix)
|
|
return console.error('Recovery time target unix is required')
|
|
|
|
await restoreFromPitr({
|
|
ref,
|
|
recovery_time_target_unix: selectedRecoveryPoint.recoveryTimeTargetUnix,
|
|
})
|
|
}
|
|
|
|
return (
|
|
<>
|
|
<FormHeader
|
|
title="Restore your database from a backup"
|
|
description="Database changes are watched and recorded, so that you can restore your database to any point in time"
|
|
/>
|
|
<BackupsStorageAlert />
|
|
{hasNoBackupsAvailable ? (
|
|
<BackupsEmpty />
|
|
) : (
|
|
<>
|
|
{hasReadReplicas && (
|
|
<Alert variant="warning">
|
|
<WarningIcon />
|
|
<AlertTitle>
|
|
Unable to restore from PITR as project has read replicas enabled
|
|
</AlertTitle>
|
|
<AlertDescription>
|
|
You will need to remove all read replicas first from your project's infrastructure
|
|
settings prior to starting a PITR restore.
|
|
</AlertDescription>
|
|
<div className="flex items-center gap-x-2 mt-2">
|
|
<Button asChild>
|
|
<Link href={`/project/${ref}/database/replication`}>Manage read replicas</Link>
|
|
</Button>
|
|
</div>
|
|
</Alert>
|
|
)}
|
|
{!showConfiguration ? (
|
|
<PITRStatus
|
|
selectedTimezone={selectedTimezone}
|
|
onUpdateTimezone={setSelectedTimezone}
|
|
onSetConfiguration={() => setShowConfiguration(true)}
|
|
/>
|
|
) : (
|
|
<PITRForm
|
|
earliestAvailableBackupUnix={earliestPhysicalBackupDateUnix}
|
|
latestAvailableBackupUnix={latestPhysicalBackupDateUnix}
|
|
onSubmit={(recoveryPoint) => {
|
|
setSelectedRecoveryPoint(recoveryPoint)
|
|
setShowConfirmation(true)
|
|
}}
|
|
/>
|
|
)}
|
|
</>
|
|
)}
|
|
|
|
<AlertDialog open={showConfirmation} onOpenChange={(open) => setShowConfirmation(open)}>
|
|
<AlertDialogContent size="medium">
|
|
<AlertDialogHeader>
|
|
<AlertDialogTitle>Point in time recovery review</AlertDialogTitle>
|
|
<AlertDialogDescription asChild>
|
|
<div className="flex flex-col space-y-2">
|
|
<p className="text-sm text-foreground-light">Your database will be restored to:</p>
|
|
<div className="py-2 flex flex-col gap-3">
|
|
<div>
|
|
<p className="text-sm font-mono text-foreground-lighter">
|
|
{selectedRecoveryPoint?.selectedTimezone.text}
|
|
</p>
|
|
<p className="text-2xl">{selectedRecoveryPoint?.recoveryTimeString}</p>
|
|
</div>
|
|
<div>
|
|
<p className="text-sm font-mono text-foreground-lighter">(UTC+00:00)</p>
|
|
<p className="text-2xl">{selectedRecoveryPoint?.recoveryTimeStringUtc}</p>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
</AlertDialogDescription>
|
|
<DialogSectionSeparator />
|
|
<DialogSection>
|
|
<Alert variant="warning">
|
|
<WarningIcon />
|
|
<AlertTitle>This action cannot be undone, not canceled once started</AlertTitle>
|
|
<AlertDescription>
|
|
Any changes made to your database after this point in time will be lost. This
|
|
includes any changes to your project's storage and authentication.
|
|
</AlertDescription>
|
|
</Alert>
|
|
</DialogSection>
|
|
<DialogSectionSeparator />
|
|
<DialogSection>
|
|
<p className="text-sm text-foreground-light">
|
|
Restores may take from a few minutes up to several hours depending on the size of
|
|
your database. During this period, your project will not be available, until the
|
|
restoration is completed.
|
|
</p>
|
|
</DialogSection>
|
|
<AlertDialogFooter>
|
|
<AlertDialogCancel>Cancel</AlertDialogCancel>
|
|
<AlertDialogAction variant="warning" onClick={onConfirmRestore}>
|
|
I understand, begin restore
|
|
</AlertDialogAction>
|
|
</AlertDialogFooter>
|
|
</AlertDialogHeader>
|
|
</AlertDialogContent>
|
|
</AlertDialog>
|
|
</>
|
|
)
|
|
}
|