The setupdb app has a mode where it'll generate fake data. The way it works is by generating a bunch of random processed crash data for a non-existent product and then putting that in postgres. There's another script for syncing that data with Elasticsearch. Pretty sure this ignore S3. Thus, fake data generation results in a state that's missing bits and who knows how that works in the webapp. I think this code isn't really helpful anymore especially in light of improvements to the local dev environment. This bug covers removing the setupdb app fake data generation code and the helper script for syncing it to Elasticsearch.
This would be good to do, but the only impact this has is "yay--less code to maintain!"
Priority: -- → P3
There's a ton of code here and a bunch of things that point to it. Removing this spaghetti noodle will do us some good. Going to tackle this today.
Assignee: nobody → willkg
Status: NEW → ASSIGNED
Commits pushed to master at https://github.com/mozilla-services/socorro https://github.com/mozilla-services/socorro/commit/aac68c90b76116a3b439ce64d11d688b669904d6 fixes bug 1398946 - remove fakedata code This removes a bunch of code we use to generate fakedata. We no longer need this, so this nixes it. https://github.com/mozilla-services/socorro/commit/8971d7c5b973814bbea88c421676a9d1f9cfb465 Merge pull request #4247 from willkg/1398946-fakedata-be-gone fixes bug 1398946 - remove fakedata code
Status: ASSIGNED → RESOLVED
Last Resolved: 3 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.