As a user, I can see what parameters were used for any task dispatched
Open
Nobody has claimed this yet.
Feature
Wishlist
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: @dralley (dalley)
Redmine Issue: 4343, https://pulp.plan.io/issues/4343
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the task record and its existing task-name and CreatedResources metadata, then determine how dispatched parameters should be recorded and exposed; done means task history explicitly shows the parameters, resource updates, remote, and mirror setting needed for auditing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100