As a user, I would like incremental export to be the same format as full export
CLOSED - CURRENTRELEASE
Currently, incremental export of a yum repo creates a series of RPM files plus JSON files. This requires users to upload the new units instead of using the existing sync functionality.
As a user, I would prefer if incremental export just created a "regular" yum repo with the updated files. This would allow me to rely on plain old sync (with config override to keep old files) to import updates instead of having a different workflow for incrementals.
NOTE: I already have code to treat incremental differently for the time being, so please let myself or someone else on Katello team know when this changes :)
Updated by firstname.lastname@example.org about 7 years ago
- Tracker changed from Issue to Story
- Groomed set to No
- Sprint Candidate set to No
Updated by ttereshc almost 7 years ago
- Status changed from NEW to POST
- Assignee set to cduryee
- Platform Release set to 2.9.0
Added by cduryee almost 7 years ago
Updated by cduryee almost 7 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset 481d40c62c6bbef5b30d23983f4cbffbcf06c85d.
Updated by email@example.com almost 7 years ago
Updated by semyers over 6 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by bmbouter almost 4 years ago
- Tags Pulp 2 added
Allow for new
incremental_export_repomdexporter distributor config option (#854)
Previously, incremental exports were in a custom format where each erratum and RPM were written to disk, along with a set of JSON files with unit metadata. This required special handling of incremental imports that was significantly different a "regular" repo sync.
This patch adds a new
incremental_export_repomddistributor option. When this is set, the incremental repo export generates metadata so that the on-disk files can be synced via the typical yum sync process. Note that you would not want to remove old units when doing this, since it would remove any units not in the incremental :koala:.
This patch also disables the repomd revision optimization if the feed URL is overriden, which allows the following sequence to work:
Without disabling the optimization, the last sync wouldn't pick up the changes. Disabling the optimization on feed URL overriding also allows recovery in this sequence:
When the optimization is disabled via feed overide, you can simply re-sync from the upstream URL to fix this :cat2:.
Fixes #1543 https://pulp.plan.io/issues/1543