Allow configuration of db-sync into MerginMaps back-office

Open
#140 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
postgresql, python
Domain
backend-api-design, databases

Research direction

The issue names no files or tests; start by tracing how db-sync currently reads project, schema, and credential configuration and how it communicates with the MerginMaps server. Use the requested project discovery and per-project settings as acceptance criteria, with synchronization working without manual configuration edits or a process restart.

Written by the indexing model from the issue text.

Description

It would be nice to be able to configure into the MerginMaps back-office:

  • The projects we want to sync
  • DB schema to use for each project
  • DB credentials ?

Currently when you add a new project you have to change the db-sync configuration and restart the process. For most companies, it is not the same role which will manage the MerginMaps projects and which will manage the db-sync deployment.

It will be great if db-sync was able to ask to the MerginMaps server the list of the projects it has to synchronize, instead of having to update the configuration.

Dominant language
Python
Stars
53
Forks
24
No merged PRs in 30d

Contributor guide

Open the contributing guide

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 MerginMaps/db-sync

All issues in MerginMaps/db-sync

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.