Project

Profile

Help

Story #4343

As a user, I can see what parameters were involved in a task

Added by dalley 9 months ago. Updated 6 months ago.

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

0%

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

Description

Presently, the task record stores two primary types of metadata about the operation it performed:

  • The name of a task (which tells you what type of task it was, sync/publish/update/etc., and where it was defined (plugin or core),
  • CreatedResources

This leaves a lot of gaps that make it impossible to properly audit the history of the state of Pulp

  • You don't know what resource was updated, or what those updates were - if it was an update task
  • You don't know what remote was used, or whether mirror=True or False - if it was a sync task
  • You can kind of figure out what the plugin type was, or what repository it was performed on, via. the name or CreatedResources, but it is implicit, not explicit.

History

#1 Updated by amacdona@redhat.com 9 months ago

+1 to add this information to tasks. However, I am not quite clear how this information will be stored and serialized. Since different "types" of tasks will have different information, its probably necessary to cram all this data into a generic field. @dalley suggested bringing back the "notes" field.

#2 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF