[M5.3] Restore anywhere

Open
  • Is something wrong?
#230 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
angular, docker, typescript
Domain
devops, infrastructure

Research direction

Start by reading ADR 0013 and the implementation of M5.2; the issue provides no file or test paths to begin from. Trace the restore flow across the control plane, agent, and web UI, then add an end-to-end test that restores to a different node. Done means that test passes; the scope also calls for new targets and scheduled restore tests.

Written by the indexing model from the issue text.

Description

priority:P1 security-review task track:agent track:control-plane track:web
Task id

M5.3

Track

C: control plane, A: agent, W: web UI

Scope
  • Restore into another node, a new database or volume; scheduled restore tests.
  • Restoring over an existing volume or database requires a confirmation token, checked by the agent (ADR 0013); restores into new targets do not.
Acceptance criteria

Restore to a different node in E2E.

Depends on

M5.2

Dominant language
TypeScript
Stars
2
Forks
1
Avg merge
7h 17m
Merged PRs (30d)
197

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from shipkeepdev/shipkeep

All issues in shipkeepdev/shipkeep

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.