This pull request continues work done in #200 to add a MutePromotionsLog model, which may help troubleshoot any imports we run once we go live (storing each imported user in a DB table vs needing to query Papertrail logs).
It also stores the original uploaded file name into the options serialized field, to make it easier to keep track of which of the 10 CSV's have been uploaded for import so far.
How should this be reviewed?
Import File view:
User view:
Any background context you want to provide?
We discussed in the Pivotal thread that we're not too worried about storage implications this may have for now (we'll be running this import for millions of users this week).
What's this PR do?
This pull request continues work done in #200 to add a
MutePromotionsLogmodel, which may help troubleshoot any imports we run once we go live (storing each imported user in a DB table vs needing to query Papertrail logs).It also stores the original uploaded file name into the
optionsserialized field, to make it easier to keep track of which of the 10 CSV's have been uploaded for import so far.How should this be reviewed?
Import File view:
User view:
Any background context you want to provide?
We discussed in the Pivotal thread that we're not too worried about storage implications this may have for now (we'll be running this import for millions of users this week).
Relevant tickets
References Pivotal #176771195.
Checklist