deployangel 0.1.22 → 0.1.23

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: edccb6c72eff7d259c14c59deaa403fb78c890cb091b40d59b080623945e1e9f
-  data.tar.gz: 364fd681c6199d591292fc67799cb6f7933da99736113ef382ff4ccf628697f8
+  metadata.gz: 2635666118ec2250b5414245e3ea0aa1026d30e4369788e2c82bf6e6b0a52f71
+  data.tar.gz: 0fac6aa9bf419e2ad7a93a289902c94fa94a6d0b42c1418d7370afbaf90501cd
 SHA512:
-  metadata.gz: 0ec79d7a8b20600e3fc57604b990749ff578a6b39bdd2caf945c8f60bf5f39ed74f3991659f8d3e26c851e8a7509cc4dabca339f36f35aaa79aca33648ba4c9d
-  data.tar.gz: 37db580510184b407f7941e6c27ad00eb956fab8df6fb59a68406753c14813bca7007de9da53ca7cf9a858f456d40f2a5da2fdd872c44bdd33997b052132ba2c
+  metadata.gz: 41f77d3e77fae4bccf35c82570582e01501246314c540d6bf6d227cdcd15e033237d62d9b0b2769e80766f53293982b4e8fe07e644ced1e99d93ca13a57b93f2
+  data.tar.gz: 674cb4c4972c88d861375904572c1048f247f041400c52b8d5380f44b3ff76d8b6f473362b404bedcf2377e1b6811cf96eea39f5cb9934b07271ddd627376afa

data/CHANGELOG.md

@@ -1,5 +1,12 @@
 # Changelog
 
+## 0.1.23 (2026-10-09)
+
+- GoodJob's cron (`config.good_job.cron`, or `GOOD_JOB_CRON`) is read from
+  the processes that run it, so its jobs are expected on schedule. Entries
+  whose schedule or class is a lambda, or that are off by default, are
+  left out; schedules without a zone are read in the server's.
+
 ## 0.1.22 (2026-10-09)
 
 - Work scheduled outside the app's own scheduler is watched too.

data/README.md

@@ -98,7 +98,8 @@ the dashboard says so.
   as it is. If your app's messages might hold personal or health data, [turn
   messages off](#exception-messages).
 - Once per process: the route table, job classes, recurring schedules
-  declared for Solid Queue, sidekiq-cron, or sidekiq-scheduler, critical
+  declared for Solid Queue, GoodJob, sidekiq-cron, sidekiq-scheduler, or
+  whenever, critical
   flows, and file digests (relative paths and hashes, never file contents) so
   DeployAngel can tell which routes changed in a release.
   Disable digests with `DEPLOYANGEL_FILE_DIGESTS=false`.
@@ -210,6 +211,13 @@ end
 Jobs that exist only in Redis, such as ones created in code or in the
 Sidekiq web UI, aren't read.
 
+GoodJob's cron (`config.good_job.cron`, or `GOOD_JOB_CRON`) is read from the
+processes that run it, the ones with cron enabled. Schedules without a zone
+are read in the server's, as GoodJob reads them. An entry whose `cron:` or
+`class:` is a lambda, or that's `enabled_by_default: false`, isn't expected.
+The agent doesn't see entries turned off in GoodJob's dashboard, so one you
+switch off there will look missed after the next deploy.
+
 #### Cron, Heroku Scheduler, and whenever
 
 Work that something outside the app starts on a schedule, such as cron,

data/lib/deployangel/rails/metadata.rb

@@ -3,7 +3,7 @@
 module DeployAngel
   module Rails
     # The Rails adapter: the route table from the router, job classes from
-    # Active Job, and Solid Queue's recurring tasks. The schedule files
+    # Active Job, and Solid Queue's and GoodJob's recurring tasks. The schedule files
     # sidekiq-cron and sidekiq-scheduler read, and the file digests, are
     # gathered in DeployAngel::Metadata.
     class Metadata < ::DeployAngel::Metadata
@@ -44,10 +44,10 @@ module DeployAngel
         []
       end
 
-      # Solid Queue's schedule is Rails' own; the rest are read the same way
-      # on every framework.
+      # Solid Queue's and GoodJob's schedules live in the Rails app; the rest
+      # are read the same way on every framework.
       def schedules
-        solid_queue_schedules + super
+        solid_queue_schedules + good_job_schedules + super
       end
 
       # Solid Queue recurring tasks for the current environment.
@@ -69,6 +69,33 @@ module DeployAngel
         []
       end
 
+      # GoodJob's cron, from a process that runs it. GoodJob turns cron on
+      # per process (often only the worker's, with GOOD_JOB_ENABLE_CRON), and
+      # its CLI applies --enable-cron after boot, before metadata is first
+      # sent. A schedule without a zone is read in the server's, as Fugit
+      # reads it. A schedule or class given as a lambda can't be known
+      # without running app code, so it's left out.
+      def good_job_schedules
+        return [] unless defined?(::GoodJob) && ::GoodJob.respond_to?(:configuration)
+
+        configuration = ::GoodJob.configuration
+        return [] unless configuration.enable_cron?
+
+        configuration.cron.filter_map do |key, entry|
+          next unless entry.is_a?(Hash)
+
+          entry = entry.transform_keys(&:to_sym)
+          cron, job_class = entry.values_at(:cron, :class)
+          job_class = job_class.name if job_class.is_a?(Module)
+          next if entry[:enabled_by_default] == false
+          next unless cron.is_a?(String) && !cron.strip.empty? && job_class.is_a?(String) && !job_class.empty?
+
+          { "key" => key.to_s, "class" => job_class, "schedule" => cron, "source" => "good_job", "time_zone" => local_time_zone }
+        end
+      rescue StandardError
+        []
+      end
+
       # A command task runs as a job of this class, so its runs show up in
       # job telemetry under that name.
       def command_job_class

data/lib/deployangel/version.rb

@@ -1,5 +1,5 @@
 # frozen_string_literal: true
 
 module DeployAngel
-  VERSION = "0.1.22"
+  VERSION = "0.1.23"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: deployangel
 version: !ruby/object:Gem::Version
-  version: 0.1.22
+  version: 0.1.23
 platform: ruby
 authors:
 - Jordan Owens