Application lifecycle: maintenance, stop, start and delete
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- angular, docker, typescript
Research direction
Start by reading the design for the Application → Danger zone actions and the existing typed agent actions; the issue does not name files or tests. Check how maintenance mode in Caddy, replica stop and start, auditing, and typed-name deletion confirmation are handled across the control plane, agent, and web UI. Done means each action meets its stated behavior, deletion requires the confirmation token, and volumes and backups are kept.
Written by the indexing model from the issue text.
Description
Track
A: agent, C: control plane, W: web UI
Scope
- Application → Danger zone actions from the design: maintenance page in Caddy, stop and start all replicas, delete with typed-name confirmation (volumes and backups kept as stated).
- Uses the existing typed agent actions only; any new action needs the ADR/SPEC process.
Acceptance criteria
Each action changes the replicas as described, is audited, and deletion needs the confirmation token.
Depends on
M1.4, M1.5
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 7h 17m
- Merged PRs (30d)
- 197
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from shipkeepdev/shipkeep
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
shipkeepdev/shipkeep#295 ·
Maintainers usually reply within 1 day
-
good first issue priority:P2 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
shipkeepdev/shipkeep#212 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority:P3 track:web
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
shipkeepdev/shipkeep#144 ·
Maintainers usually reply within 1 day
-
documentation good first issue priority:P3 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
shipkeepdev/shipkeep#143 ·
Maintainers usually reply within 1 day
-
enhancement good first issue priority:P3 track:control-plane
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
shipkeepdev/shipkeep#142 ·
Maintainers usually reply within 1 day
All issues in shipkeepdev/shipkeep
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
jeanibarz/knowledge-base-mcp-server#1268 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 78/100
Koenkk/zigbee-herdsman-converters#13820 ·
Maintainers usually reply within 2 days
-
[prefer-expect-resolves] autofix leaves a stray ")" when the awaited expression is parenthesizedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
jest-community/eslint-plugin-jest#2052 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Wallet functions throws TypeError when the wallet has no account IDPossibly taken @Medhansh-741 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
hiero-ledger/hiero-sdk-js#4781 · 1 comment ·
Maintainers usually reply within 1 day