kennel 1.142.0 → 1.143.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 4d3462f8e8c88a8faab007c9d65f799703152083c59f9b1f726eb7f958efb743
-  data.tar.gz: f24f0df2e733292cb32cedfe257cb7393b8403f35585ede6fb008fd9e7668bb4
+  metadata.gz: 352765b10b857aa4e8d8a4fa27de59a8be5800208bcebbf76b78b6321fff48cd
+  data.tar.gz: 83428c482b87caca3dacc21645c493cfc8d6002e881ca792e4cb75281c51249d
 SHA512:
-  metadata.gz: 75b7f56baabbffc696d44acae8d08277afd499fd1915f1f268a7ffd9010ff9fc6f1ae59c06f54a78d1b3e49829d9ec61f0d98fd16ac00d85ef494451339fe3e2
-  data.tar.gz: a5c96201475a76c9712313cbfc1bfbd629f87748d2d8d101dc3413ebc72a5399b18291df8fab64f6162c3e534fda17f6069d12fd380fc2c5e32c635f7a8bab13
+  metadata.gz: 79fd182dc92c9f9dd4fbdf04000c16cd0e01a613935c552780de02ff0a512a31d87cfe3a0c3e4551d3d6245ce3ea5859b293a0547dcbd66a826e6fc8e2afbbeb
+  data.tar.gz: b3ea7f3c6f1c883aa64da4a5a56615caaffd5179ea45fac5aa17584d44017ae454318e28fd783c323fbe363372ded94b58f7e6ea7098aa0e58f0706ba15a26e7

data/Readme.md

@@ -198,7 +198,6 @@ end
 
 ### Updating an existing monitor
  - use [datadog monitor UI](https://app.datadoghq.com/monitors/manage) to find a monitor
- - get the `id` from the url
  - run `URL='https://app.datadoghq.com/monitors/123' bundle exec rake kennel:import` and copy the output
  - import task also works with SLO alerts, e.g. `URL='https://app.datadoghq.com/slo/edit/123abc456def123/alerts/789' bundle exec rake kennel:import`
  - find or create a project in `projects/`
@@ -249,7 +248,6 @@ Remove the code that created the resource. The next update will delete it (see a
 
 ### Updating an existing dashboard
  - go to [datadog dashboard UI](https://app.datadoghq.com/dashboard/lists) and click on _New Dashboard_ to find a dashboard
- - get the `id` from the url
  - run `URL='https://app.datadoghq.com/dashboard/bet-foo-bar' bundle exec rake kennel:import` and copy the output
  - find or create a project in `projects/`
  - add a dashboard to `parts: [` list, for example:

data/lib/kennel/api.rb

@@ -129,7 +129,7 @@ module Kennel
         if !response.success? && (response.status != 404 || !ignore_404)
           message = +"Error #{response.status} during #{method.upcase} #{path}\n"
           message << "request:\n#{JSON.pretty_generate(body)}\nresponse:\n" if body
-          message << response.body
+          message << response.body.encode(message.encoding, invalid: :replace, undef: :replace)
           raise message
         end
 

data/lib/kennel/models/monitor.rb

@@ -26,7 +26,8 @@ module Kennel
         groupby_simple_monitor: false,
         variables: nil,
         on_missing_data: "default", # "default" is "evaluate as zero"
-        notification_preset_name: nil
+        notification_preset_name: nil,
+        notify_by: nil
       }.freeze
       DEFAULT_ESCALATION_MESSAGE = ["", nil].freeze
       ALLOWED_PRIORITY_CLASSES = [NilClass, Integer].freeze
@@ -35,7 +36,7 @@ module Kennel
         :query, :name, :message, :escalation_message, :critical, :type, :renotify_interval, :warning, :timeout_h, :evaluation_delay,
         :ok, :no_data_timeframe, :notify_no_data, :notify_audit, :tags, :critical_recovery, :warning_recovery, :require_full_window,
         :threshold_windows, :scheduling_options, :new_host_delay, :new_group_delay, :priority, :variables, :on_missing_data,
-        :notification_preset_name
+        :notification_preset_name, :notify_by
       )
 
       defaults(
@@ -59,7 +60,8 @@ module Kennel
         priority: -> { MONITOR_DEFAULTS.fetch(:priority) },
         variables: -> { MONITOR_OPTION_DEFAULTS.fetch(:variables) },
         on_missing_data: -> { MONITOR_OPTION_DEFAULTS.fetch(:on_missing_data) },
-        notification_preset_name: -> { MONITOR_OPTION_DEFAULTS.fetch(:notification_preset_name) }
+        notification_preset_name: -> { MONITOR_OPTION_DEFAULTS.fetch(:notification_preset_name) },
+        notify_by: -> { MONITOR_OPTION_DEFAULTS.fetch(:notify_by) }
       )
 
       def build_json
@@ -109,6 +111,11 @@ module Kennel
           end
         end
 
+        # set without causing lots of nulls to be stored
+        if notify_by_value = notify_by
+          options[:notify_by] = notify_by_value
+        end
+
         # setting this via the api breaks the UI with
         # "The no_data_timeframe option is not allowed for log alert monitors"
         if data.fetch(:type) == "log alert"

data/lib/kennel/version.rb

@@ -1,4 +1,4 @@
 # frozen_string_literal: true
 module Kennel
-  VERSION = "1.142.0"
+  VERSION = "1.143.1"
 end

data/template/Readme.md

@@ -180,7 +180,6 @@ end
 
 ### Updating an existing monitor
  - use [datadog monitor UI](https://app.datadoghq.com/monitors/manage) to find a monitor
- - get the `id` from the url
  - run `URL='https://app.datadoghq.com/monitors/123' bundle exec rake kennel:import` and copy the output
  - import task also works with SLO alerts, e.g. `URL='https://app.datadoghq.com/slo/edit/123abc456def123/alerts/789' bundle exec rake kennel:import`
  - find or create a project in `projects/`
@@ -231,7 +230,6 @@ Remove the code that created the resource. The next update will delete it (see a
 
 ### Updating an existing dashboard
  - go to [datadog dashboard UI](https://app.datadoghq.com/dashboard/lists) and click on _New Dashboard_ to find a dashboard
- - get the `id` from the url
  - run `URL='https://app.datadoghq.com/dashboard/bet-foo-bar' bundle exec rake kennel:import` and copy the output
  - find or create a project in `projects/`
  - add a dashboard to `parts: [` list, for example:

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: kennel
 version: !ruby/object:Gem::Version
-  version: 1.142.0
+  version: 1.143.1
 platform: ruby
 authors:
 - Michael Grosser
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2023-06-06 00:00:00.000000000 Z
+date: 2023-08-21 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: diff-lcs
@@ -135,14 +135,14 @@ required_ruby_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
-      version: 3.1.0
+      version: 3.2.0
 required_rubygems_version: !ruby/object:Gem::Requirement
   requirements:
   - - ">="
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.3.26
+rubygems_version: 3.4.10
 signing_key:
 specification_version: 4
 summary: Keep datadog monitors/dashboards/etc in version control, avoid chaotic management