Files
supabase/apps/studio/components/ui/ProjectUpgradeFailedBanner.tsx
Jordi Enric 18b273cde0 fix(studio): hide Postgres Version Upgrade logs behind a flag (#48007)
## Problem

The legacy Logs Explorer's Postgres Version Upgrade page (Database
Operations section) shows no results for most users. pg_upgrade_logs
rows aren't tagged with the project attribute the shared logs endpoint
scopes on, only a host field, so the project-scoped query returns
nothing even though the data exists.

## Fix

Hides the Database Operations sidebar section behind a new
showPostgresUpgradeLogs feature flag (default off), following the same
pattern as showMultigresLogs. The page route itself is untouched, only
the sidebar entry point is gated.

## How to test

- With the flag off, open the legacy Logs Explorer sidebar and confirm
the Database Operations section and Postgres Version Upgrade item are
gone
- With the flag on, confirm the section and item render as before

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

## Summary by CodeRabbit

* **New Features**
* Added conditional access to Postgres Version Upgrade logs based on
feature availability.
* Failed Postgres upgrade notifications now show a “View logs” option
only when supported.

* **Bug Fixes**
* Prevented unsupported Postgres upgrade log links and navigation
options from appearing.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->
2026-07-17 10:07:00 +02:00

82 lines
2.8 KiB
TypeScript

import { SupportCategories } from '@supabase/shared-types/out/constants'
import { DatabaseUpgradeStatus } from '@supabase/shared-types/out/events'
import { useParams } from 'common'
import dayjs from 'dayjs'
import { Button } from 'ui'
import { Admonition } from 'ui-patterns/admonition'
import { InlineLink } from './InlineLink'
import { SupportLink } from '@/components/interfaces/Support/SupportLink'
import { useProjectUpgradingStatusQuery } from '@/data/config/project-upgrade-status-query'
import { useShowPostgresUpgradeLogs } from '@/hooks/misc/useShowPostgresUpgradeLogs'
import { IS_PLATFORM } from '@/lib/constants'
import { guessLocalTimezone } from '@/lib/dayjs'
// [Joshen] Think twice about the category though - it doesn't correspond
export const ProjectUpgradeFailedBanner = () => {
const { ref } = useParams()
const { data } = useProjectUpgradingStatusQuery({ projectRef: ref }, { enabled: IS_PLATFORM })
const { status, initiated_at, latest_status_at, error } = data?.databaseUpgradeStatus ?? {}
const showPostgresUpgradeLogs = useShowPostgresUpgradeLogs()
const isFailed = status === DatabaseUpgradeStatus.Failed
const initiatedAt = dayjs
.utc(initiated_at ?? 0)
.tz(guessLocalTimezone())
.format('DD MMM YYYY HH:mm:ss')
const subject = 'Upgrade failed for project'
const message = `Upgrade information:\n• Initiated at: ${initiated_at}\n• Error: ${error}`
const initiatedAtEncoded = encodeURIComponent(
dayjs.utc(initiated_at ?? 0).format('YYYY-MM-DDTHH:mm:ss')
)
const latestStatusAtEncoded = encodeURIComponent(
dayjs
.utc(latest_status_at ?? 0)
.utcOffset(0)
.format('YYYY-MM-DDTHH:mm:ss')
)
const timestampFilter = `its=${initiatedAtEncoded}&ite=${latestStatusAtEncoded}`
if (!isFailed) return null
return (
<div className="max-w-7xl">
<Admonition
type="warning"
title={`Postgres version upgrade was not successful (Initiated at ${initiatedAt})`}
actions={
<Button asChild variant="default">
<SupportLink
queryParams={{
category: SupportCategories.DATABASE_UNRESPONSIVE,
projectRef: ref,
subject,
message,
}}
>
Contact support
</SupportLink>
</Button>
}
>
<div>
Your project and its data are not affected. Please reach out to us via our support form
for assistance with the upgrade.
</div>
{showPostgresUpgradeLogs && (
<div>
You may also view logs related to the failed upgrade in your{' '}
<InlineLink href={`/project/${ref}/logs/pg-upgrade-logs?${timestampFilter}`}>
project's logs
</InlineLink>
.
</div>
)}
</Admonition>
</div>
)
}