mirror of
https://github.com/discourse/discourse.git
synced 2026-08-08 17:53:55 +08:00
fb9bb31983This 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>
33 lines
1.1 KiB
Ruby
Vendored
33 lines
1.1 KiB
Ruby
Vendored
# frozen_string_literal: true
|
|
|
|
# Intended to be called from UpcomingChanges::Track service,
|
|
# not standalone.
|
|
#
|
|
# Lookup any event_type: added (0) events and compare with removed (1) events
|
|
# * If there are any added that are no longer in SiteSetting.upcoming_change_site_settings
|
|
# with no corresponding removed (1) event, create a removed event for them.
|
|
#
|
|
# We do not need to notify admins about removed changes.
|
|
class UpcomingChanges::Action::TrackRemovedChanges < Service::ActionBase
|
|
def call
|
|
previously_added_changes.filter_map do |change_name|
|
|
next if SiteSetting.upcoming_change_site_settings.include?(change_name)
|
|
next if previously_removed_changes.include?(change_name)
|
|
|
|
UpcomingChangeEvent.create!(event_type: :removed, upcoming_change_name: change_name)
|
|
change_name
|
|
end
|
|
end
|
|
|
|
private
|
|
|
|
def previously_added_changes
|
|
@previously_added_changes ||=
|
|
UpcomingChangeEvent.added.pluck(:upcoming_change_name).uniq.map(&:to_sym)
|
|
end
|
|
|
|
def previously_removed_changes
|
|
@previously_removed_changes ||=
|
|
UpcomingChangeEvent.removed.pluck(:upcoming_change_name).uniq.map(&:to_sym)
|
|
end
|
|
end
|
