Skip to content

postgres: document current clone and restore flow - #930

Merged
frodesundby merged 1 commit into
mainfrom
docs/postgres-clone-and-restore
Nov 18, 2026
Merged

frodesundby merged 1 commit into
mainfrom
docs/postgres-clone-and-restore

Conversation

@frodesundby

Copy link
Copy Markdown
Contributor

Summary

  • Remove the retired Postgres branch concept, branch selection and activation instructions, and obsolete CLI flags.
  • Document cloning and point-in-time restore through the current CLI and Console, including local time handling and the default clone point about 10 minutes ago.
  • Add a cloning reference covering inherited settings, resource overrides, recovery limits and completion status.
  • Update extension availability and Console configuration support, personal access levels, and deletion safeguards for dependent clones.

Validation

  • Checked behavior against the current CLI, Console and pgrator implementations.
  • All 54 svdoc tests pass.
  • NAV production build passes in a temporary clean copy with a frozen-lockfile install, including these documentation changes.
  • Local Markdown link targets exist; extension tables match all 34 selectable extensions in pgrator.
  • git diff --check passes.

The existing workspace build failure was traced to a stale local cookie@0.6.0 shadowing the locked cookie@2.0.2. A clean installation builds successfully; no application code or dependencies are changed in this PR.

@frodesundby
frodesundby merged commit f209cd1 into main Nov 18, 2026
7 checks passed
@frodesundby
frodesundby deleted the docs/postgres-clone-and-restore branch November 18, 2026 12:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant