Story #7297
As a user, I can perform an import without creating the destination repo(s) in advance
Status:
NEW
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 107
Quarter:
Description
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
History
#1
Updated by daviddavis about 1 year 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
#4
Updated by ipanova@redhat.com 5 months ago
whenever this is in place docs should be updated https://github.com/pulp/pulpcore/pull/1396
#5
Updated by ipanova@redhat.com 4 months 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
#9
Updated by ipanova@redhat.com 3 months ago
- Sprint changed from Sprint 101 to Sprint 102
#11
Updated by rchan about 2 months ago
- Sprint changed from Sprint 103 to Sprint 104
#12
Updated by rchan about 1 month ago
- Sprint changed from Sprint 104 to Sprint 105
Please register to edit this issue
.