Closed Bug 1697001 Opened 2 years ago Closed 5 months ago

get rid of UnredactedCrash API and model

Categories

(Socorro :: Webapp, task, P3)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: willkg, Assigned: willkg)

References

Details

Attachments

(1 file)

Socorro has a ProcessedCrash API as well as an UnredactedCrash API. The difference between the two is that the UnredactedCrash API includes exploitability data.

When we grant protected data access to individuals, that also includes exploitability data. Further, when creating an API token, you can opt to grant it exploitability data access or not. Thus there's no substantial difference between these two API endpoints.

I can never remember what UnredactedCrash API does and I have to look it up every time. It's implemented as a subclass of the ProcessedCrash API.

This bug covers looking into whether we can fold the difference into ProcessedCrash, update all the Socorro uses of UnredactedCrash, and get rid of this extra API.

Grabbing this to do now since it simplifies the permissions overhaul work I'm doing.

Assignee: nobody → willkg
Blocks: 1764395
Status: NEW → ASSIGNED

willkg merged PR #6144: "bug 1697001: remove UnredactedCrash API" in 25a748b.

Before this gets deployed to production, we should send out an email about how we're removing the UnredactedCrash API and people should switch to using ProcessedCrash API.

I deployed this to prod just now in bug #1787851. Marking as FIXED.

I'll notify stability and crashreporting-wg.

Status: ASSIGNED → RESOLVED
Closed: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.