Story #9225: Add comps.xml upload support - RPM Support - Pulp

Actions

Send by e-mail Copy link

Story #9225

closed

Add comps.xml upload support

Added by Skullman over 3 years ago. Updated about 3 years ago.

Status:

CLOSED - DUPLICATE

Priority:

Normal

Assignee:

ggainey

Sprint/Milestone:

3.17.0

Start date:

Due date:

% Done:

100%

Estimated time:

Platform Release:

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 108

Quarter:

Q4-2021

Description

Ticket moved to GitHub: "pulp/pulp_rpm/2313":https://github.com/pulp/pulp_rpm/issues/2313

In RHUI3 (Pulp 2) it is possible to upload comps.xml metadata into custom repository using API: self.pulp.upload_api.import_upload(upload_id, repo_id, TYPE_ID_PKG_GROUP, unit_key, metadata)

Actions

Copy link

Updated by dalley over 3 years ago

This is a very-nice-to-have item for RHUI and technically a feature gap with Pulp 2

Actions

Copy link

Updated by dalley about 3 years ago

Sprint set to Sprint 107
Quarter set to Q4-2021

Actions

Copy link

Updated by rchan about 3 years ago

Sprint changed from Sprint 107 to Sprint 108

Actions

Copy link

Updated by pulpbot about 3 years ago

Status changed from NEW to POST

PR: https://github.com/pulp/pulp_rpm/pull/2159

Actions

Copy link

Updated by ggainey about 3 years ago

PR #2159 implements the following REST call/behavior at POST /pulp/api/v3/rpm/comps/ :

file= [required] : full path to a comps.xml file.
repository= [optional] : rpm_repository_href, a repository to add the resulting comps-Content-units to
replace= [optional] : boolean, used only if repository= specified. If true, creates a new repo-version in the repository by first removing existing comps-Content from repository.latest_version() and then adding the ones contained in file=.

The pulp_hrefs of all comps-Content found in file= are returned in created_resources, even if they already existed. If repository= is specified, the pulp_href of the new repository-version is also in created_resources. This may change before the PR is merged, however.

Skullman - how does this sound to you? Does it meet your needs? Or do you need the specific comps-Content-units be independently createable (ie, PackageGroup, PackageEnvironment, PackageLangpack, PackageCategory all with their own POST calls?)

Actions

Copy link