Upgrade to Noticed 2.3.2

[pJeyakumar]

Upgrade to Noticed 2.3.2. (from Noticed 1.6.0)

• coupled with all of the necessary code changes, file naming, and migrations to maintain same functionality of the application

[pJeyakumar]

Discussion w/ Jon:

1. Push the migration through.
2. Upgrade Noticed gem (1.6.0 -> 2.3.2), make all the necessary code adjustments, and ApplicationJob to create new notifications from the old notifications.
   • Run the ApplicationJob manually and during off hours to go through all of the old notifications.
   • Have a section to display jobs that are currently running
3. Remove the ApplicationJob
4. DROP the old notifications table (maybe, after some time has passed)

---

Considerations:

1. Staging's db refreshes based on Production every 24h (meaning if testing and migration takes longer than 24h, our new notification records would be wiped, since Production does not have those records yet)
2. May need to increase the hourly email limit in Staging (currently is 50 emails per hour).
   • Since we'll need to test a variety of Notifications and Mailers.
3. Need to update Anony to exclude noticed_events and noticed_notifications
4. Create RSpec tests for Notification classes

---

Next Steps:

1. Run the migration first and then upgrade to the Noticed 2.3.2 gem.
   • to determine that there will be no issues if the tables already exist when we're making the code changes

UPDATE:

After Run the migration first and then upgrade to the Noticed 2.3.2 gem.

• There was no issue found. After Run the migration first and then upgrade to the Noticed 2.3.2 gem. and making all the necessary code adjustments and running the ApplicationJob and then reverting back to our 1st state, with Noticed 1.6.0
• There were no issues found. The application worked normally and all old notifications were accessible.
• The only caveat is that any new notifications that were created after the code changes and BEFORE the revert do not exist.
  • Something we could do to combat this is to create an ApplicationJob to create an old notifications record for every new notifications record that was created BEFORE we revert to Noticed 1.6.0.