Actions
Task #8182
closed
Add an `AccessPolicy.customized` field to tell if a user has customized one or not
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:
Description
Problem¶
Developers ship a default access policy and users can customize it. At some point later developers will need to adjust the default policy, but this should only happen if a user has not already customized it. Right now it would be difficult to determine if the user customized it or not.
Solution¶
Add a field to AccessPolicy called customized which defaults to False. Any user change to the policy will set this to True.
Related issues
Updated by ipanova@redhat.com about 3 years ago
- Sprint/Milestone set to 3.10.0
let's use customized as agreed per open floor
Updated by bmbouter about 3 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to bmbouter
Updated by bmbouter about 3 years ago
- Subject changed from Add an `AccessPolicy.modified` field to tell if a user has customized one or not to Add an `AccessPolicy.customized` field to tell if a user has customized one or not
- Description updated (diff)
Updated by bmbouter about 3 years ago
- Blocked by Task #8203: Fix all migrations to use `apps.get_model(...)` instead of directly importing the model added
Updated by pulpbot about 3 years ago
- Status changed from ASSIGNED to POST
Added by bmbouter about 3 years ago
Updated by bmbouter about 3 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|d5ce8e6ff9d3ef1e13f89229293cc6bcb216c105.
Updated by pulpbot about 3 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
.
Adds the
AccessPolicy.customizedfield.The
AccessPolicy.customizedfields is a read-only field that defaults to False. If True, it indicates that the user has modified the policy.This will be useful for:
closes #8182