Actions
Issue #7756
closedContent upload has different method-definintion than rpm/file/etc.
Status:
CLOSED - WONTFIX
Priority:
Low
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version - Debian:
Platform Release:
Target Release - Debian:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
API Bindings, Katello
Sprint:
Quarter:
Description
Looking at the generated API-Bindings for ruby, the method for creating/uploading a new deb-package differs from the one used for e.g. rpm.
module PulpDebClient
class ContentPackagesApi
...
def create(opts = {})
While in the RPM-bindings it looks like this:
module PulpRpmClient
class ContentPackagesApi
...
def create(relative_path, opts = {})
The fact that relative_path
is specified as parameter in the latter case seems to be due to the fact that in the API, relative_path
is marked as required in pulp_rpm, but not in pulp_deb.
https://pulp-deb.readthedocs.io/en/latest/restapi.html#operation/content_deb_packages_create
https://pulp-rpm.readthedocs.io/en/latest/restapi.html#operation/content_rpm_packages_create
THis came up during the katello integration of pulp_deb for pulpcore.
Actions