I'd like it if exclusion profiles returned a timestamp of the most recent time they were updated.
This would help me do things like notify all clients when the active exclusion profiles have been update <somewhere else>, prompting them to refresh to pick up the new changes.
Mauro said he'd take a look at this sometime next week, because Mauro is good people. :)
Assignee: nobody → mdoglio
Mauro, ping? :)
Created attachment 8659861 [details] [review] PR 957
Attachment #8659861 - Flags: review?(emorley)
To land this on staging/production we need a bit of coordination because there's a db change.
Commit pushed to master at https://github.com/mozilla/treeherder https://github.com/mozilla/treeherder/commit/120ae4fadac274e59c20c1ab671d628417be3961 Bug 1194824 - Add last modified timestamp to ExclusionProfile
I applied these db schema changes to both staging and production: alter table `exclusion_profile` add column `modified` datetime default CURRENT_TIMESTAMP; alter table `exclusion_profile` modify column `modified` datetime NOT NULL;
I actually set `DEFAULT CURRENT_TIMESTAMP` so that we don't get errors before we land the code: alter table `exclusion_profile` modify column `modified` datetime default CURRENT_TIMESTAMP;
(In reply to Mauro Doglio [:mdoglio] from comment #7) > I applied these db schema changes to both staging and production: Could you also update Heroku's RDS instance please :-)
Ooops I forgot about the heroku deployment. Done.
Thank you :-)
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.