Project

Profile

Help

Issue #7520

Pulp2 API import_upload endpoint with input of tag name and digest

Added by sajha about 1 month ago. Updated 30 days ago.

Status:
CLOSED - NOTABUG
Priority:
Normal
Assignee:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Platform Release:
OS:
Triaged:
No
Groomed:
No
Sprint Candidate:
No
Tags:
Katello
Sprint:
Quarter:

Description

With pulp2 we were using the /actions/import_upload/ endpoint with params for tag name and digest for a manifest to tag a manifest. This is used in hammer today with pulp2 to upload tags.

I am not aware of a similar flow with pulp3 and could we add it if not currently implemented. The flow with pulp2 upload tag is we created an uplaod request and then call import upload with a tag name and a digest value for the manifest we need to tag.

Let me know if additional context is needed around this. For reference, In pulp2, the exact call from our binding that does this is here: https://github.com/Katello/runcible/blob/4a3b3118f77dc6a70d2ca499cbce483e3af32131/lib/runcible/resources/content.rb#L42

History

#1 Updated by ipanova@redhat.com 30 days ago

  • Status changed from NEW to CLOSED - NOTABUG

Hi, there is a feature parity in pulp3 for tagging and untagging. Please reference these docs https://pulp-container.readthedocs.io/en/latest/workflows/manage-content.html#tagging

Please register to edit this issue

Also available in: Atom PDF