Import existing pgEdge Starfleet databases and branches as servers
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
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
- Ships a Dockerfile or Docker Compose file
- No 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 pgadmin-org/pgadmin4
-
Invalid syntax in sshtunnelPossibly taken A pull request linked to this issue is open or already merged. OpenBug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
pgadmin-org/pgadmin4#10797 ·
Maintainers usually reply within 2 days
-
Feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgadmin-org/pgadmin4#10426 · 3 comments · 1 reaction ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 25/100
pgadmin-org/pgadmin4#10796 · 1 comment ·
Maintainers usually reply within 2 days
-
Schema Diff does not detect foreign keys that reference a different schemaPossibly taken @dpage claimed this today. Open
Difficulty 4/5 3-5 days Newbie friendliness 57/100
pgadmin-org/pgadmin4#10786 · 1 assignee ·
Maintainers usually reply within 2 days
-
Bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
pgadmin-org/pgadmin4#10783 ·
Maintainers usually reply within 2 days
All issues in pgadmin-org/pgadmin4
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
mohanraj00/entelos#200 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
sweep
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
bketelsen/truenas-mcp#77 ·
Maintainers usually reply within 1 day
-
Console writes URL credentials to the local log, though AGENTS.md says secrets never reach diskOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
sandbox-quantum/switch#2163 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
openedx/xblock-lti-consumer#765 ·
Maintainers usually reply within 1 day