Make export/import process simpler for CLI
@ggainey ya está trabajando en esto.
Desde el 25/1/2023.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Users should be able to export the repositories they want in one command and shouldn't need to know the difference between 'export' and 'exporter'. I propose we remove the 'export' commands and re-brand them under 'exporter'. Exporter should get two new subcommands: 'export' and 'history'.
The 'history' command would get three subcommands from the original 'export' command: 'list', 'show', and 'delete'. Export objects are basically history records of previous exports and thus would fit nicely under this context. If a user doesn't specify a subcommand when using 'history' the default behaviour should be 'list' so they can see all the export objects aka the history.
The new 'export' sub command will take over the original export's 'run' command. This command will have extra functionality to allow for the creation of an exporter so the whole process can be done in one command.
Examples:
with Exporter named foo:
$pulp exporter pulp export --name foo [export options]
Started export task. Task href: ...
with no Exporter:
$pulp exporter pulp export --base-path tmp/exports/ --repository file_repo file --repository rpm_repo rpm [export options]
Would you like to save these configurations? [y/n]
$y
Please give a name to the exporter config options:
$bar
Config options saved in exporter object bar
Started export task. Task href: ...
If the user would specify 'no' on saving the config options, the command would give the created exporter a default name. The other commands under 'exporter' should have their help descriptions updated to reflect the exporter's role as a config object.
A similar process should be applied to the 'importer' commands so that the experience is consistent.
- Lenguaje dominante
- Python
- Estrellas
- 43
- Forks
- 52
- Merge medio
- 11 h 38 min
- PR fusionados (30 d)
- 11
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de pulp/pulp-cli
-
bug Triage-Needed
Dificultad 2/5 1-3 horas Aptitud para principiantes 58/100
-
For RPM repositories support setting package_signing_service and package_signing_fingerprint Abierto
Dificultad 3/5 1-2 días Aptitud para principiantes 45/100
-
feature request
Dificultad 4/5 3-5 días Aptitud para principiantes 35/100
-
easy fix feature request
Dificultad 3/5 1-2 días Aptitud para principiantes 25/100
-
bug Triage-Needed
Dificultad 4/5 3-5 días Aptitud para principiantes 42/100
Todos los issues de pulp/pulp-cli
Issues similares
-
[Bug] reef-hermes tells me to resume with hermes --resume, which does not work from my shell Abiertoarea: harness bug status: needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Human-Agent-Society/reef#625 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 80/100
learningequality/kolibri#15351 · 2 comentarios ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
-
Name consistency Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
eellak/triplestore#65 · 1 comentario ·