chef 18.10.17 → 19.2.12

data/lib/chef/resource/inspec_waiver.rb

@@ -1,5 +1,5 @@
 #
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -19,92 +19,93 @@ require_relative "../resource"
 class Chef
   class Resource
     class InspecWaiver < Chef::Resource
-      provides :inspec_waiver
+      provides :inspec_waiver, target_mode: true
+      target_mode support: :full
 
       description "Use the **inspec_waiver** resource to add a waiver to the Compliance Phase."
       introduced "17.5"
       examples <<~DOC
-        **Activate the default waiver in the openssh cookbook's compliance segment**:
+      **Activate the default waiver in the openssh cookbook's compliance segment**:
 
-        ```ruby
-          inspec_waiver 'openssh' do
-            action :add
-          end
-        ```
+      ```ruby
+        inspec_waiver 'openssh' do
+          action :add
+        end
+      ```
 
-        **Activate all waivers in the openssh cookbook's compliance segment**:
+      **Activate all waivers in the openssh cookbook's compliance segment**:
 
-        ```ruby
-          inspec_waiver 'openssh::.*' do
-            action :add
-          end
-        ```
+      ```ruby
+        inspec_waiver 'openssh::.*' do
+          action :add
+        end
+      ```
 
-        **Add an InSpec waiver to the Compliance Phase**:
+      **Add an InSpec waiver to the Compliance Phase**:
 
-        ```ruby
-          inspec_waiver 'Add waiver entry for control' do
-            control 'my_inspec_control_01'
-            run_test false
-            justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
-            expiration '2022-01-01'
-            action :add
-          end
-        ```
+      ```ruby
+        inspec_waiver 'Add waiver entry for control' do
+          control 'my_inspec_control_01'
+          run_test false
+          justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
+          expiration '2022-01-01'
+          action :add
+        end
+      ```
 
-        **Add an InSpec waiver to the Compliance Phase using the 'name' property to identify the control**:
+      **Add an InSpec waiver to the Compliance Phase using the 'name' property to identify the control**:
 
-        ```ruby
-          inspec_waiver 'my_inspec_control_01' do
-            justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
-            action :add
-          end
-        ```
+      ```ruby
+        inspec_waiver 'my_inspec_control_01' do
+          justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
+          action :add
+        end
+      ```
 
-        **Add an InSpec waiver to the Compliance Phase using an arbitrary YAML, JSON, or TOML file**:
+      **Add an InSpec waiver to the Compliance Phase using an arbitrary YAML, JSON, or TOML file**:
 
-        ```ruby
-          # files ending in .yml or .yaml that exist are parsed as YAML
-          inspec_waiver "/path/to/my/waiver.yml"
+      ```ruby
+        # files ending in .yml or .yaml that exist are parsed as YAML
+        inspec_waiver "/path/to/my/waiver.yml"
 
-          inspec_waiver "my-waiver-name" do
-            source "/path/to/my/waiver.yml"
-          end
+        inspec_waiver "my-waiver-name" do
+          source "/path/to/my/waiver.yml"
+        end
 
-          # files ending in .json that exist are parsed as JSON
-          inspec_waiver "/path/to/my/waiver.json"
+        # files ending in .json that exist are parsed as JSON
+        inspec_waiver "/path/to/my/waiver.json"
 
-          inspec_waiver "my-waiver-name" do
-            source "/path/to/my/waiver.json"
-          end
+        inspec_waiver "my-waiver-name" do
+          source "/path/to/my/waiver.json"
+        end
 
-          # files ending in .toml that exist are parsed as TOML
-          inspec_waiver "/path/to/my/waiver.toml"
+        # files ending in .toml that exist are parsed as TOML
+        inspec_waiver "/path/to/my/waiver.toml"
 
-          inspec_waiver "my-waiver-name" do
-            source "/path/to/my/waiver.toml"
-          end
-        ```
+        inspec_waiver "my-waiver-name" do
+          source "/path/to/my/waiver.toml"
+        end
+      ```
 
-        **Add an InSpec waiver to the Compliance Phase using a hash**:
+      **Add an InSpec waiver to the Compliance Phase using a hash**:
 
-        ```ruby
-          my_hash = { "ssh-01" => {
-            "expiration_date" => "2033-07-31",
-            "run" => false,
-            "justification" => "because"
-          } }
+      ```ruby
+        my_hash = { "ssh-01" => {
+          "expiration_date" => "2033-07-31",
+          "run" => false,
+          "justification" => "because"
+        } }
 
-          inspec_waiver "my-waiver-name" do
-            source my_hash
-          end
-        ```
+        inspec_waiver "my-waiver-name" do
+          source my_hash
+        end
+      ```
 
-        Note that the **inspec_waiver** resource does not update and will not fire notifications (similar to the log resource). This is done to preserve the ability to use
-        the resource while not causing the updated resource count to be larger than zero. Since the resource does not update the state of the managed node, this behavior
-        is still consistent with the configuration management model. Instead, you should use events to observe configuration changes for the compliance phase. It is
-        possible to use the `notify_group` resource to chain notifications of the two resources, but notifications are the wrong model to use, and you should use pure ruby
-        conditionals instead. Compliance configuration should be independent of other resources and should only be conditional based on state/attributes, not other resources.
+      Note that the **inspec_waiver** resource does not update and will not fire notifications (similar to the log resource). This is done to preserve the ability to use
+      the resource while not causing the updated resource count to be larger than zero. Since the resource does not update the state of the managed node, this behavior
+      is still consistent with the configuration management model. Instead, you should use events to observe configuration changes for the compliance phase. It is
+      possible to use the `notify_group` resource to chain notifications of the two resources, but notifications are the wrong model to use, and you should use pure ruby
+      conditionals instead. Compliance configuration should be independent of other resources and should only be conditional based on state/attributes, not other resources.
       DOC
 
       property :control, String,

data/lib/chef/resource/inspec_waiver_file_entry.rb

@@ -1,6 +1,6 @@
 #
 # Author:: Davin Taddeo (<davin@chef.io>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -23,40 +23,41 @@ require "chef-utils/dist" unless defined?(ChefUtils::Dist)
 class Chef
   class Resource
     class InspecWaiverFileEntry < Chef::Resource
-      provides :inspec_waiver_file_entry
+      provides :inspec_waiver_file_entry, target_mode: true
+      target_mode support: :full
 
       description "Use the **inspec_waiver_file_entry** resource to add or remove entries from an InSpec waiver file. This can be used in conjunction with the Compliance Phase."
       introduced "17.1"
       examples <<~DOC
-        **Add an InSpec waiver entry to a given waiver file**:
-
-        ```ruby
-          inspec_waiver_file_entry 'Add waiver entry for control' do
-            file_path 'C:\\chef\\inspec_waiver_file.yml'
-            control 'my_inspec_control_01'
-            run_test false
-            justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
-            expiration '2022-01-01'
-            action :add
-          end
-        ```
+      **Add an InSpec waiver entry to a given waiver file**:
+
+      ```ruby
+        inspec_waiver_file_entry 'Add waiver entry for control' do
+          file_path 'C:\\chef\\inspec_waiver_file.yml'
+          control 'my_inspec_control_01'
+          run_test false
+          justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
+          expiration '2022-01-01'
+          action :add
+        end
+      ```
 
-        **Add an InSpec waiver entry to a given waiver file using the 'name' property to identify the control**:
+      **Add an InSpec waiver entry to a given waiver file using the 'name' property to identify the control**:
 
-        ```ruby
-          inspec_waiver_file_entry 'my_inspec_control_01' do
-            justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
-            action :add
-          end
-        ```
+      ```ruby
+        inspec_waiver_file_entry 'my_inspec_control_01' do
+          justification "The subject of this control is not managed by #{ChefUtils::Dist::Infra::PRODUCT} on the systems in policy group \#{node['policy_group']}"
+          action :add
+        end
+      ```
 
-        **Remove an InSpec waiver entry to a given waiver file**:
+      **Remove an InSpec waiver entry to a given waiver file**:
 
-        ```ruby
-          inspec_waiver_file_entry "my_inspec_control_01" do
-            action :remove
-          end
-        ```
+      ```ruby
+        inspec_waiver_file_entry "my_inspec_control_01" do
+          action :remove
+        end
+      ```
       DOC
 
       property :control, String,

data/lib/chef/resource/ips_package.rb

@@ -1,6 +1,6 @@
 #
 # Author:: Jason Williams (<williamsjj@digitar.com>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -23,8 +23,9 @@ class Chef
   class Resource
     class IpsPackage < ::Chef::Resource::Package
 
-      provides :ips_package
-      provides :package, os: "solaris2"
+      provides :ips_package, target_mode: true
+      provides :package, os: "solaris2", target_mode: true
+      target_mode support: :full
 
       description "Use the **ips_package** resource to manage packages (using Image Packaging System (IPS)) on the Solaris 11 platform."
 

data/lib/chef/resource/kernel_module.rb

@@ -4,7 +4,7 @@
 # The MIT License (MIT)
 #
 # Copyright:: 2016-2018, Shopify Inc.
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 
 require_relative "../resource"
 
@@ -12,7 +12,8 @@ class Chef
   class Resource
     class KernelModule < Chef::Resource
 
-      provides :kernel_module
+      provides :kernel_module, target_mode: true
+      target_mode support: :full
 
       description "Use the **kernel_module** resource to manage kernel modules on Linux systems. This resource can load, unload, blacklist, disable, enable, install, and uninstall modules."
       introduced "14.3"
@@ -232,7 +233,7 @@ class Chef
         # see if the module is listed in /proc/modules or not
         # @return [Boolean]
         def module_loaded?
-          /^#{new_resource.modname}/.match?(::File.read("/proc/modules"))
+          /^#{new_resource.modname}/.match?(::TargetIO::File.read("/proc/modules"))
         end
       end
     end

data/lib/chef/resource/ksh.rb

@@ -1,6 +1,6 @@
 #
 # Author:: Nolan Davidson (<nolan.davidson@gmail.com>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -22,7 +22,8 @@ class Chef
   class Resource
     class Ksh < Chef::Resource::Script
 
-      provides :ksh
+      provides :ksh, target_mode: true
+      target_mode support: :full
 
       description "Use the **ksh** resource to execute scripts using the Korn shell (ksh)" \
                   " interpreter. This resource may also use any of the actions and properties" \

data/lib/chef/resource/launchd.rb

@@ -136,7 +136,7 @@ class Chef
         description: "Sets the log mask to `LOG_DEBUG` for this job."
 
       property :disabled, [ TrueClass, FalseClass ], default: false,
-        description: "Hints to `launchctl` to not submit this job to launchd."
+               description: "Hints to `launchctl` to not submit this job to launchd."
 
       property :enable_globbing, [ TrueClass, FalseClass ],
         description: "Update program arguments before invocation."

data/lib/chef/resource/link.rb

@@ -1,7 +1,7 @@
 #
 # Author:: Adam Jacob (<adam@chef.io>)
 # Author:: Tyler Cloke (<tyler@chef.io>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -25,7 +25,8 @@ class Chef
     class Link < Chef::Resource
       include Chef::Mixin::Securable
 
-      provides :link
+      provides :link, target_mode: true
+      target_mode support: :full
 
       description "Use the **link** resource to create symbolic or hard links.\n\n" \
                   "A symbolic link—sometimes referred to as a soft link—is a directory entry" \
@@ -46,7 +47,7 @@ class Chef
         description: "An optional property to set the target file if it differs from the resource block's name.",
         name_property: true
 
-      property :to, String,
+      property :to, [String, nil],
         description: "The actual file to which the link is to be created."
 
       property :link_type, [String, Symbol],

data/lib/chef/resource/locale.rb

@@ -1,6 +1,6 @@
 #
 # Copyright:: 2011-2016, Heavy Water Software Inc.
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -21,24 +21,25 @@ require "chef-utils/dist" unless defined?(ChefUtils::Dist)
 class Chef
   class Resource
     class Locale < Chef::Resource
-      provides :locale
+      provides :locale, target_mode: true
+      target_mode support: :full
 
       description "Use the **locale** resource to set the system's locale on Debian and Windows systems. Windows support was added in Chef Infra Client 16.0"
       introduced "14.5"
 
       examples <<~DOC
-        Set the lang to 'en_US.UTF-8'
+      Set the lang to 'en_US.UTF-8'
 
-        ```ruby
-          locale 'set system locale' do
-            lang 'en_US.UTF-8'
-          end
-        ```
+      ```ruby
+        locale 'set system locale' do
+          lang 'en_US.UTF-8'
+        end
+      ```
       DOC
 
       LC_VARIABLES ||= %w{LC_ADDRESS LC_COLLATE LC_CTYPE LC_IDENTIFICATION LC_MEASUREMENT LC_MESSAGES LC_MONETARY LC_NAME LC_NUMERIC LC_PAPER LC_TELEPHONE LC_TIME}.freeze
       LOCALE_CONF ||= "/etc/locale.conf".freeze
-      LOCALE_REGEX ||= /\A\S+/.freeze
+      LOCALE_REGEX ||= /\A\S+/
       LOCALE_PLATFORM_FAMILIES ||= %w{debian windows}.freeze
 
       property :lang, String,
@@ -79,7 +80,7 @@ class Chef
           lang get_system_locale_windows
         else
           begin
-            old_content = ::File.read(LOCALE_CONF)
+            old_content = ::TargetIO::File.read(LOCALE_CONF)
             locale_values = Hash[old_content.split("\n").map { |v| v.split("=") }]
             lang locale_values["LANG"]
           rescue Errno::ENOENT => e

data/lib/chef/resource/log.rb

@@ -1,7 +1,7 @@
 #
 # Author:: Cary Penniman (<cary@rightscale.com>)
 # Author:: Tyler Cloke (<tyler@chef.io>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -31,6 +31,8 @@ class Chef
     class Log < Chef::Resource
 
       provides :log, target_mode: true
+      target_mode support: :full,
+        introduced: "15.1"
 
       description "Use the **log** resource to create log entries. The log resource behaves" \
                   " like any other resource: built into the resource collection during the" \

data/lib/chef/resource/lwrp_base.rb

@@ -2,7 +2,7 @@
 # Author:: Adam Jacob (<adam@chef.io>)
 # Author:: Christopher Walters (<cw@chef.io>)
 # Author:: Daniel DeLeo (<dan@chef.io>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");

data/lib/chef/resource/macos_pkg.rb

@@ -1,7 +1,7 @@
 #
 # Author:: Joshua Timberman (<jtimberman@chef.io>)
 # Author:: William Theaker (<william.theaker+chef@gusto.com>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.

data/lib/chef/resource/macos_userdefaults.rb

@@ -1,6 +1,6 @@
 #
 # Copyright:: 2011-2018, Joshua Timberman
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.

data/lib/chef/resource/macports_package.rb

@@ -1,6 +1,6 @@
 #
 # Author:: David Balatero (<dbalatero@gmail.com>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");

data/lib/chef/resource/mdadm.rb

@@ -31,49 +31,49 @@ class Chef
                   " and then by using the mount provider to create a file systems table (fstab) entry."
 
       examples <<~DOC
-        **Create and assemble a RAID 0 array**
+      **Create and assemble a RAID 0 array**
 
-        The mdadm command can be used to create RAID arrays. For example, a RAID 0 array named /dev/md0 with 10 devices would have a command similar to the following:
+      The mdadm command can be used to create RAID arrays. For example, a RAID 0 array named /dev/md0 with 10 devices would have a command similar to the following:
 
-        ```
-        mdadm --create /dev/md0 --level=0 --raid-devices=10 /dev/s01.../dev/s10
-        ```
+      ```
+      mdadm --create /dev/md0 --level=0 --raid-devices=10 /dev/s01.../dev/s10
+      ```
 
-        where /dev/s01 .. /dev/s10 represents 10 devices (01, 02, 03, and so on). This same command, when expressed as a recipe using the mdadm resource, would be similar to:
+      where /dev/s01 .. /dev/s10 represents 10 devices (01, 02, 03, and so on). This same command, when expressed as a recipe using the mdadm resource, would be similar to:
 
-        ```ruby
-        mdadm '/dev/md0' do
-          devices [ '/dev/s01', ... '/dev/s10' ]
-          level 0
-          action :create
-        end
-        ```
+      ```ruby
+      mdadm '/dev/md0' do
+        devices [ '/dev/s01', ... '/dev/s10' ]
+        level 0
+        action :create
+      end
+      ```
 
-        (again, where /dev/s01 .. /dev/s10 represents devices /dev/s01, /dev/s02, /dev/s03, and so on).
+      (again, where /dev/s01 .. /dev/s10 represents devices /dev/s01, /dev/s02, /dev/s03, and so on).
 
-        **Create and assemble a RAID 1 array**
+      **Create and assemble a RAID 1 array**
 
-        ```ruby
-        mdadm '/dev/md0' do
-          devices [ '/dev/sda', '/dev/sdb' ]
-          level 1
-          action [ :create, :assemble ]
-        end
-        ```
+      ```ruby
+      mdadm '/dev/md0' do
+        devices [ '/dev/sda', '/dev/sdb' ]
+        level 1
+        action [ :create, :assemble ]
+      end
+      ```
 
-        **Create and assemble a RAID 5 array**
+      **Create and assemble a RAID 5 array**
 
-        The mdadm command can be used to create RAID arrays. For example, a RAID 5 array named /dev/sd0 with 4, and a superblock type of 0.90 would be similar to:
+      The mdadm command can be used to create RAID arrays. For example, a RAID 5 array named /dev/sd0 with 4, and a superblock type of 0.90 would be similar to:
 
-        ```ruby
-        mdadm '/dev/sd0' do
-          devices [ '/dev/s1', '/dev/s2', '/dev/s3', '/dev/s4' ]
-          level 5
-          metadata '0.90'
-          chunk 32
-          action :create
-        end
-        ```
+      ```ruby
+      mdadm '/dev/sd0' do
+        devices [ '/dev/s1', '/dev/s2', '/dev/s3', '/dev/s4' ]
+        level 5
+        metadata '0.90'
+        chunk 32
+        action :create
+      end
+      ```
       DOC
 
       default_action :create

data/lib/chef/resource/mount.rb

@@ -1,7 +1,7 @@
 #
 # Author:: Joshua Timberman (<joshua@chef.io>)
 # Author:: Tyler Cloke (<tyler@chef.io>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -24,7 +24,9 @@ class Chef
     class Mount < Chef::Resource
       description "Use the **mount** resource to manage a mounted file system."
 
-      provides :mount
+      provides :mount, target_mode: true
+      target_mode support: :full,
+        platforms: %i{aix bsd linux}
 
       default_action :mount
       allowed_actions :mount, :umount, :unmount, :remount, :enable, :disable
@@ -41,11 +43,11 @@ class Chef
         sensitive: true
 
       property :mount_point, String, name_property: true,
-        coerce: proc { |arg| (arg == "/" || arg.match?(":/$")) ? arg : arg.chomp("/") }, # Removed "/" from the end of str, because it was causing idempotency issue.
-        description: "The directory (or path) in which the device is to be mounted. Defaults to the name of the resource block if not provided."
+               coerce: proc { |arg| (arg == "/" || arg.match?(":/$")) ? arg : arg.chomp("/") }, # Removed "/" from the end of str, because it was causing idempotency issue.
+               description: "The directory (or path) in which the device is to be mounted. Defaults to the name of the resource block if not provided."
 
       property :device, String, identity: true,
-        description: "Required for `:umount` and `:remount` actions (for the purpose of checking the mount command output for presence). The special block device or remote node, a label, or a uuid to be mounted."
+               description: "Required for `:umount` and `:remount` actions (for the purpose of checking the mount command output for presence). The special block device or remote node, a label, or a uuid to be mounted."
 
       property :device_type, [String, Symbol],
         description: "The type of device: :device, :label, or :uuid",

data/lib/chef/resource/msu_package.rb

@@ -1,6 +1,6 @@
 #
 # Author:: Nimisha Sharad (<nimisha.sharad@msystechnologies.com>)
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 # License:: Apache License, Version 2.0
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
@@ -54,7 +54,7 @@ class Chef
         default: lazy { package_name }
 
       property :checksum, String, desired_state: false,
-        description: "SHA-256 digest used to verify the checksum of the downloaded MSU package."
+               description: "SHA-256 digest used to verify the checksum of the downloaded MSU package."
 
       property :timeout, [String, Integer],
         default: 3600,

data/lib/chef/resource/notify_group.rb

@@ -1,5 +1,5 @@
 #
-# Copyright:: Copyright (c) Chef Software Inc.
+# Copyright:: Copyright (c) 2009-2026 Progress Software Corporation and/or its subsidiaries or affiliates. All Rights Reserved.
 #
 # Licensed under the Apache License, Version 2.0 (the "License");
 # you may not use this file except in compliance with the License.
@@ -19,7 +19,8 @@ require_relative "../resource"
 class Chef
   class Resource
     class NotifyGroup < Chef::Resource
-      provides :notify_group
+      provides :notify_group, target_mode: true
+      target_mode support: :full
 
       description "The notify_group resource does nothing, and always fires notifications which are set on it.  Use it to DRY blocks of notifications that are common to multiple resources, and provide a single target for other resources to notify.  Unlike most resources, its default action is :nothing."
       introduced "15.8"