Extension of Python REST API (repo index, metrics, content filters)
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- Python
- Sterne
- 49
- Forks
- 88
- Ø Merge
- 1 T. 10 Std.
- Gemergte PRs (30 T.)
- 31
Beschreibung
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.
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
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.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- postgresql, python
- Bereich
- api, backend
- Issue-Typ
- Feature
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Aktiv
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 52/100