discourse/app/services/notification/action/bulk_create.rb
Martin Brennan fb9bb31983
FEATURE: Notify admins of upcoming changes and log events (#37003)
This commit adds several pieces of functionality to help keep admins
in the loop about upcoming changes.

First of all, there is a new initializer on boot that will notify admins
about
newly available upcoming changes, as well as log removed changes and
status movement of existing changes.

* When there is a new upcoming change, we only notify admins about
   it when the status is the `promote_upcoming_changes_on_status` - 1,
   e.g. if `promote_upcoming_changes_on_status` is `beta` then we only
   tell admin about the change once it has reached `alpha`. This means
   we may log the `added` event in one deploy, but only actually notify
   admins in a subsequent deploy.
* We log removed upcoming changes so we can automatically delete old
   site setting data in a future job as needed.

We also now  notify  admins when  upcoming changes are automatically
promoted to enabled based on the site's
`promote_upcoming_changes_on_status`:

<img width="378" height="600" alt="image"
src="https://github.com/user-attachments/assets/4200fbee-9990-4bbc-a378-85946e631e77"
/>

In addition, we now show an indicator in the admin sidebar
if there are new upcoming changes that have been added since
they last visited the upcoming change config page. This data
is stored in a user custom field, because Redis is ephemeral,
and storing in the User table is overkill because 99% of users
are not staff:

<img width="248" height="112" alt="image"
src="https://github.com/user-attachments/assets/4c3d3cf7-ac39-45f8-a2c8-a049cb85b8e9"
/>

Finally, this commit moves both the Track and Promote initializer
logic behind a `DistributedMutex`, we don't want multiple processes
running the same logic here, it needs to be only once.

---------

Co-authored-by: Loïc Guitaut <loic@discourse.org>
Co-authored-by: Joffrey JAFFEUX <j.jaffeux@gmail.com>
2026-01-21 12:45:54 +10:00

83 lines
2.4 KiB
Ruby
Vendored

# frozen_string_literal: true
# Bulk creates notifications using insert_all! for efficiency, then manually
# handles the after_commit callbacks that would normally run on individual creates:
# - MessageBus notification state publishing per user
# - Email processing via NotificationEmailer
# - DiscourseEvent.trigger(:notification_created, notification)
#
# @example
# Notification::Action::BulkCreate.call(
# records: [
# { user_id: 1, notification_type: Notification.types[:custom], data: "{}".to_json },
# { user_id: 2, notification_type: Notification.types[:custom], data: "{}".to_json },
# ]
# )
#
class Notification::Action::BulkCreate < Service::ActionBase
# Array of notification attribute hashes.
# Required keys: :user_id, :notification_type, :data
# Optional keys: :topic_id, :post_number, :high_priority
option :records
# Skip email sending for all notifications
option :skip_send_email, default: -> { false }
def call
return [] if records.blank?
insert_notifications
publish_notification_states
post_process_notifications
@notification_ids
end
private
def insert_notifications
now = Time.zone.now
rows =
records.map do |record|
{
user_id: record[:user_id],
notification_type: record[:notification_type],
data: record[:data],
topic_id: record[:topic_id],
post_number: record[:post_number],
high_priority:
record[:high_priority] ||
Notification.high_priority_types.include?(record[:notification_type]),
read: false,
created_at: now,
updated_at: now,
}
end
result = Notification.insert_all!(rows, returning: %i[id user_id])
@notification_ids = result.rows.map(&:first)
@user_ids_from_insert = result.rows.map(&:second).uniq
end
def publish_notification_states
User.where(id: @user_ids_from_insert).find_each(&:publish_notifications_state)
end
def post_process_notifications
Notification
.where(id: @notification_ids)
.includes(:user)
.find_each do |notification|
if !skip_send_email
if notification.user.do_not_disturb?
ShelvedNotification.create(notification_id: notification.id)
else
NotificationEmailer.process_notification(notification)
end
end
DiscourseEvent.trigger(:notification_created, notification)
end
end
end