Import existing pgEdge Starfleet databases and branches as servers

Open
#10,747 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

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
postgresql, python
Domain
backend, database

Research direction

Start by reading issue #10746, which covers signing in, then trace the existing Deploy Cloud Instance flow that registers a server and the Register Server dialog. The requested work includes listing Starfleet databases and branches, selecting a server group, updating existing entries instead of duplicating them, and handling IP allowlists; the issue names no files or tests. Done means selected databases and branches are imported with connection details and allowlist guidance.

Written by the indexing model from the issue text.

Description

pgAdmin only knows about a pgEdge Starfleet database if it was created through the Deploy Cloud Instance wizard, which registers the new server at the end. Anyone with existing databases or branches has to copy the host, port, database name and credentials from the pgEdge Starfleet console into the Register Server dialog by hand, once for every database and again for every branch.

Once signed in (see #10746), pgAdmin should list the user's pgEdge Starfleet databases and branches and add the ones they select as servers in a server group of their choice, with the connection details filled in. Importing the same database again should update the existing server rather than add a duplicate. Where a pgEdge Starfleet IP allowlist would stop pgAdmin connecting, pgAdmin should say so, and offer to add its address to the database's allowlist where pgEdge Starfleet allows that.

Dominant language
Python
Stars
3.9k
Forks
922
Avg merge
2d 3h
Merged PRs (30d)
33

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 pgadmin-org/pgadmin4

All issues in pgadmin-org/pgadmin4

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.