Actions
Story #7297
closed
As a user, I can perform an import without creating the destination repo(s) in advance
Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:
0%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
GalaxyNG
Sprint:
Sprint 112
Quarter:
Description
Ticket moved to GitHub: "pulp/pulpcore/1920":https://github.com/pulp/pulpcore/issues/1920
A couple options we discussed:
- Do this by default if the destination repo(s) don't exist
- Create a flag (eg create_repos_on_import) that a user can use to trigger this behavior
Updated by daviddavis over 2 years ago
- Subject changed from As a user, I can perform an import with creating the destination repo(s) in advance to As a user, I can perform an import without creating the destination repo(s) in advance
Updated by ipanova@redhat.com almost 2 years ago
whenever this is in place docs should be updated https://github.com/pulp/pulpcore/pull/1396
Updated by ipanova@redhat.com almost 2 years ago
- Sprint set to Sprint 98
This story blocks the import/export for pulp-container push repos. These repos are being automatically created during 'podman push' operation, alongside with the distribution which is going to serve the repo. Container push repos cannot be created via API. Import requires destination repos to be created/present in advance. The solution is to enable import to create missing destination repos on the fly whether automatically inside the task(1) or by specifying a flag(2) - TBD
Updated by ipanova@redhat.com over 1 year ago
- Sprint changed from Sprint 101 to Sprint 102
Updated by pulpbot about 1 year ago
- Description updated (diff)
- Status changed from NEW to CLOSED - DUPLICATE
Actions
.