Convert celery task repo.importer.set_importer to Pulp 3
CLOSED - DUPLICATE
- Related to Task #2380: Create a redmine task for each 2.y celery task to be converted to 3.0 added
Thinking about this now, maybe this one does not need to be a task.
If a repo does not have an importer, it cannot be doing a sync/copy/upload, so there is no need to have the resource lock on the repo before adding the importer.
What about the case where the set_importer is replacing an existing importer? Does that ever happen?
I do not think we should support a replace operation. CRUD should be sufficient.
If you try to create a document that already exists, that's an error.
Is this task needed or would it be addressed by the implementation of #2402?
- Status changed from NEW to CLOSED - DUPLICATE
This work will be entirely handled by #2402.
- Is duplicate of Story #2402: As an API user, a call to update an Importer generates a Task added
- Sprint/Milestone set to 3.0.0
Please register to edit this issue
Also available in: Atom