Story #5184
closedProvide identifier within sync task progress_reports
100%
Description
Problem¶
Currently the progress reports on a sync task look like this:
progress_reports:
- message: Downloading Metadata
state: running
total: 10
done: 5
suffix:
- message: Downloading Artifacts
state: running
total: 10
done: 5
suffix:
- message: Associating Content
state: running
total: 10
done: 5
suffix:
when trying to parse these, we have to use the 'message' field which is english text. This text is internationalized and could be different system, to system, or if a user changes their language settings post installation.
It would be better if there was some 'key' that we could use such as 'associate.content' that we could be assured would never change or be affected by internationalization.
Solution¶
Add a required field to ProgressReport named code
that stores a 36 character long string. The intent of this string is that it identifies that type of progress report. It's different than the pk of the progress report which is different between two runs of the same task. This ID would be the same for all runs of that task code. It would not be internationalized.
36 is chosen in case the user wants to store UUIDs in this field.
Updated by bmbouter over 5 years ago
- Tracker changed from Issue to Story
- Subject changed from provide identifier within sync task progress_reports to Provide identifier within sync task progress_reports
- Description updated (diff)
- % Done set to 0
Updated by bmbouter over 5 years ago
- Description updated (diff)
Updating to code
after some IRC discussion w/ @daviddavis
Updated by daviddavis over 5 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Updated by fao89 about 5 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to fao89
Updated by fao89 about 5 years ago
- Status changed from ASSIGNED to POST
Added by Fabricio Aguiar about 5 years ago
Added by Fabricio Aguiar about 5 years ago
Revision 0c1c563b | View on GitHub
identifying the type of progress report
closes #5184 Required PR: https://github.com/pulp/pulp_file/pull/272 Required PR: https://github.com/pulp/pulpcore-plugin/pull/123 https://pulp.plan.io/issues/5184
Updated by Anonymous about 5 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|0c1c563b6e5f28279ab1515b83bc6368ba761262.
Added by Fabricio Aguiar about 5 years ago
Revision 56fe3fb2 | View on GitHub
adding code on progress bar
ref #5184 https://pulp.plan.io/issues/5184 Required PR: https://github.com/pulp/pulpcore-plugin/pull/123 Required PR: https://github.com/pulp/pulpcore/pull/289
Added by Fabricio Aguiar about 5 years ago
Revision 64c14710 | View on GitHub
adding code on progress bar
ref #5184 https://pulp.plan.io/issues/5184 Required PR: https://github.com/pulp/pulpcore-plugin/pull/123 Required PR: https://github.com/pulp/pulpcore/pull/289
Added by Fabricio Aguiar about 5 years ago
Revision b6e8c7f5 | View on GitHub
adding code on progress bar
ref #5184 https://pulp.plan.io/issues/5184 Required PR: https://github.com/pulp/pulpcore-plugin/pull/123 Required PR: https://github.com/pulp/pulpcore/pull/289
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by ggainey over 4 years ago
- Tags Katello added
- Tags deleted (
Katello-P3)
Updated by bmbouter over 4 years ago
- Category deleted (
14)
We are removing the 'API' category per open floor discussion June 16, 2020.
adding code on progress bar
ref #5184 https://pulp.plan.io/issues/5184 Required PR: https://github.com/pulp/pulpcore-plugin/pull/123 Required PR: https://github.com/pulp/pulpcore/pull/289