Actions
Task #7776
closed
Document to not use setting in the model fields
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Documentation, Easy Fix
Sprint:
Sprint 97
Quarter:
Q2-2021
Description
Problem¶
Settings should not be used in the models fields
- https://github.com/pulp/pulp_container/pull/170/files#diff-1707426fbe1933a12da3490e42f0dbceea79e47f7c883708c0b0cb49755b1d94L383
- https://github.com/pulp/pulpcore/blob/master/pulpcore/app/models/upload.py#L23
Proposal¶
Add to the plugin writers docs to not use settings in the models fields but rather 'hardcode' those values, since settings can change which will lead to a data migration
Updated by ipanova@redhat.com over 1 year ago
- Status changed from NEW to ASSIGNED
- Assignee set to ipanova@redhat.com
- Sprint set to Sprint 97
Updated by pulpbot over 1 year ago
- Status changed from ASSIGNED to POST
Added by ipanova@redhat.com over 1 year ago
Updated by ipanova@redhat.com over 1 year ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|f5d1a3e6cbb00f0e6c6f49c4d82ff3abb204e908.
Updated by pulpbot over 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Updated plugin writers' guide to not use settings directly in the model fields.
closes #7776