[M5.1] Managed databases

Open
#228 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
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
mariadb, mongodb, mysql, postgresql, redis, typescript

Research direction

Start by reading the implementations and acceptance criteria for dependencies M4.2 and M3.7 to understand the control plane, agent, and web UI work this task builds on. The scope covers five database engines, version selection, secret credentials, connection string injection, and lifecycle behavior. Done means each engine can be created, connected to from an app, and restarted without data loss.

Written by the indexing model from the issue text.

Description

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

M5.1

Track

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

Scope
  • PostgreSQL, MySQL, MariaDB, MongoDB, Redis with versions, credentials as secrets, connection string injection.
Acceptance criteria

Each engine created, connected from an app, restarted without data loss.

Depends on

M4.2, M3.7

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.