The Backup Summary card offered a Restore button even when the restore
source held no backups: enabled with a warning in point-in-time mode,
disabled in snapshot mode. Neither reads as "there is nothing to restore
from yet" - which the card already says, two lines above. Hide the block
instead, and keep the disabled-with-a-reason button for the cases a user
can do something about, the member's "ask an organization admin" included.

Deciding that from `get_restore_availability` would have hidden it from
members too: that function reports no backups for every refusal, a
permission refusal among them. `mark_restore_sources` already walks the
groups the rule selects, so it answers the question instead.

Once the source instance is gone the cutover is over, and the "Restored
from" card is advice nobody can still act on. Demote it to Metadata, next
to Created At - the same kind of fact - and drop the next steps with it.
Metadata is server-rendered from the database, so provenance survives a
control plane the Backups accordion could not reach.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

tobru changed title from ~~WIP: Self-Service Restore into new Instance~~ to Self-Service Restore into new Instance

2026-09-18 12:08:23 +00:00

tobru merged commit b590d9d11c into main

2026-09-18 12:08:42 +00:00

tobru deleted branch feat/self-service-restore

2026-09-18 12:08:42 +00:00

tobru referenced this pull request from a commit

2026-09-18 12:08:44 +00:00

Merge pull request 'Self-Service Restore into new Instance' (#678) from feat/self-service-restore into main

tobru referenced this pull request

2026-09-18 12:09:04 +00:00

PostgreSQL Backup Self-Service Restore #613