Project

Profile

Help

Story #2402

As an API user, a call to update an Importer generates a Task

Added by ttereshc almost 3 years ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 21

Description

We need to create an update task which can live in pulp.app.tasks.importer.

Task name in Pulp 2: `pulp.server.managers.repo.importer.update_importer_config`.
Task implementation in Pulp 2: https://github.com/pulp/pulp/blob/3.0-dev/server/pulp/server/controllers/importer.py#L240


Checklist


Related issues

Related to Pulp - Task #2380: Create a redmine task for each 2.y celery task to be converted to 3.0 CLOSED - CURRENTRELEASE Actions
Duplicated by Pulp - Task #2401: Convert celery task repo.importer.set_importer to Pulp 3 CLOSED - DUPLICATE Actions

Associated revisions

Revision f92a4255 View on GitHub
Added by dkliban@redhat.com over 2 years ago

Problem: importer updates are performed syncronously

Solution: override the update method in the Importer viewset

The update method now dispatches a task to update the importer.

closes #2402
https://pulp.plan.io/issues/2402

Revision f92a4255 View on GitHub
Added by dkliban@redhat.com over 2 years ago

Problem: importer updates are performed syncronously

Solution: override the update method in the Importer viewset

The update method now dispatches a task to update the importer.

closes #2402
https://pulp.plan.io/issues/2402

Revision f92a4255 View on GitHub
Added by dkliban@redhat.com over 2 years ago

Problem: importer updates are performed syncronously

Solution: override the update method in the Importer viewset

The update method now dispatches a task to update the importer.

closes #2402
https://pulp.plan.io/issues/2402

History

#1 Updated by ttereshc almost 3 years ago

  • Related to Task #2380: Create a redmine task for each 2.y celery task to be converted to 3.0 added

#2 Updated by ttereshc almost 3 years ago

  • Tags Pulp 3 added

#3 Updated by mhrivnak almost 3 years ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

#4 Updated by mhrivnak almost 3 years ago

This comment also applies here: https://pulp.plan.io/issues/2409#note-4

#5 Updated by bmbouter over 2 years ago

  • Tracker changed from Task to Story
  • Subject changed from Convert celery task repo.importer.update_importer_config to Pulp 3 to As an API user, a call to update an importer generates a Task
  • Description updated (diff)

Rewriting based on similarity to issue 2756 and discussion on the mailing list: https://www.redhat.com/archives/pulp-dev/2017-May/msg00014.html

#6 Updated by bmbouter over 2 years ago

  • Subject changed from As an API user, a call to update an importer generates a Task to As an API user, a call to update an Importer generates a Task

#7 Updated by mhrivnak over 2 years ago

  • Sprint/Milestone set to 39

#8 Updated by bmbouter over 2 years ago

  • Duplicated by Task #2401: Convert celery task repo.importer.set_importer to Pulp 3 added

#9 Updated by dkliban@redhat.com over 2 years ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to dkliban@redhat.com

#10 Updated by mhrivnak over 2 years ago

  • Sprint/Milestone changed from 39 to 40

#11 Updated by dkliban@redhat.com over 2 years ago

  • Status changed from ASSIGNED to POST

#12 Updated by dkliban@redhat.com over 2 years ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#13 Updated by bmbouter over 1 year ago

  • Sprint set to Sprint 21

#14 Updated by bmbouter over 1 year ago

  • Sprint/Milestone deleted (40)

#15 Updated by daviddavis 6 months ago

  • Sprint/Milestone set to 3.0

#16 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF