-
-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create SystemLimit data model #35675
base: master
Are you sure you want to change the base?
Conversation
1dcd3e5
to
31d5c99
Compare
0f55c33
to
0e9386f
Compare
Cal happened to give me drive by thoughts on this, and mentioned that moving feature limits from settings to a model makes it harder to track changes (very fair point). The django admin does track who made changes and when, but that does not include actual values of the limit. We could add the field audit decorator to this model if we are interested in tracking changes over time, which I'm tempted to do. |
That sounds like a good idea. |
last_modified is not needed since it can be determined via audit events
This field is really only intended for extreme circumstances when we want to either increase or decrease a specific domain's limit
Sorry for all of the new commits. This is ready for review now. |
Product Description
Technical Summary
Simple SQL table to hold onto limits for features. It is easier to update these via django admin than putting them in settings and having to run cchq commands, so that is the main inspiration for this change. This just introduces the model.
Feature Flag
Safety Assurance
Safety story
Very safe. Just adding a new table.
Automated test coverage
QA Plan
No
Migrations
Rollback instructions
Labels & Review