Extension of Python REST API (repo index, metrics, content filters)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Python
- Estrellas
- 49
- Forks
- 88
- Merge medio
- 1 d 10 h
- PR fusionados (30 d)
- 31
Descripción
Lightwell UI lists Python packages, versions, and repository counts through content-sources-backend. That backend reads Pulp Postgres directly (Tangy). We need Pulp HTTP APIs so the path is UI → backend → Pulp REST, not SQL.
Today GET …/content/python/packages/ is one row per file (wheel + sdist). It cannot paginate distinct package names or return versions per package.
{pk} is the repository UUID. Latest complete repository version is implied.
| UI path | Pulp |
|---|---|
| PackageList | New GET …/repositories/python/python/{pk}/packages/ — one row per name_normalized, paginate, name_normalized__istartswith |
| PackageVersions | Extend existing GET …/content/python/packages/ with collapse_builds=true and serializer field base_version (still use packagetype=sdist) |
| PackageGet | Existing content list (name + version + packagetype=sdist); add base_version on the serializer. Omit collapse_builds. |
| RepoMetrics | New GET …/repositories/python/python/{pk}/metrics/ — package_count, version_count, build_count |
collapse_builds=true (default false): strip trailing \.[a-zA-Z]+-\d+$ from version, one row per (name_normalized, base_version).
PackageList rows: name, name_normalized, versions[], latest_releases[] (version, created_at, release). Same version keys in both lists. Pulp-native shape, not Tangy DTOs.
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.
Línea de trabajo
Start by tracing the existing GET …/content/python/packages/ endpoint and its serializer, then locate the repository package and metrics API entry points described in the issue. Done means the new and extended Pulp REST responses support the specified pagination, filters, collapse behavior, fields, and package/version/build counts without relying on Tangy DTOs.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- postgresql, python
- Área
- api, backend
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Activo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 52/100