Closed
Bug 1100352
Opened 10 years ago
Closed 2 years ago
Remove hard-coded allow lists from ProcessedCrash and RawCrash models
Categories
(Socorro :: Webapp, task)
Socorro
Webapp
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: adrian, Assigned: willkg)
References
Details
We should rely on our Super Search Fields list and remove the hard-coded white lists of fields in our ProcessedCrash and RawCrash models. However, before doing so, we need to audit our current list to make sure no field was forgotten, so that we don't accidentally remove fields from exposure in our public API.
Comment 1•7 years ago
|
||
Does this issue require just removing the white lists in ProcessedCrash and RawCrash models?
If so, could I work on this issue? It seems relatively easy.
https://github.com/mozilla-services/socorro/blob/e3263f0f678c481017289d92188b0daa8b4a0fe4/webapp-django/crashstats/crashstats/models.py#L605-L654
https://github.com/mozilla-services/socorro/blob/e3263f0f678c481017289d92188b0daa8b4a0fe4/webapp-django/crashstats/crashstats/models.py#L721-L794
Flags: needinfo?(peterbe)
Assignee | ||
Comment 2•7 years ago
|
||
Issei: At some point, I want to tackle this, but not quiet, yet. I think this requires some careful architecture work before we can make code changes.
Flags: needinfo?(peterbe)
Comment 3•7 years ago
|
||
Thanks for your comment, Will!
I see. I'll find another issue to work on.
Assignee | ||
Updated•4 years ago
|
Summary: Remove hard-coded white lists from ProcessedCrash and RawCrash models → Remove hard-coded allow lists from ProcessedCrash and RawCrash models
Assignee | ||
Comment 4•2 years ago
|
||
I removed the allow list for the ProcessedCrash API in 683ef8d2.
Still have to do the RawCrash API.
Depends on: 1764395
Assignee | ||
Comment 5•2 years ago
|
||
Grabbing this to do soon.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Assignee | ||
Comment 6•2 years ago
|
||
The allow list for the RawCrash API was removed in adda44e8.
All done here!
You need to log in
before you can comment on or make changes to this bug.
Description
•