Import existing pgEdge Starfleet databases and branches as servers

Abierto
#10,747 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 2 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
postgresql, python
Área
backend, database

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
3.9k
Forks
922
Merge medio
2 d 3 h
PR fusionados (30 d)
33

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de pgadmin-org/pgadmin4

Todos los issues de pgadmin-org/pgadmin4

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.