summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorRanjib Dey <ranjib@pagerduty.com>2015-06-23 23:13:12 -0700
committerRanjib Dey <ranjib@pagerduty.com>2015-06-24 10:12:45 -0700
commit720f3331f794a2ad31bee2b1113ac99fada85389 (patch)
tree4f03dfd86d9fb543cb2eaf1b6a4c3848d356b11f /RELEASE_NOTES.md
parent9f0ea8aa0ec05819e242dedaa85fe731dca3146c (diff)
parentab34e3cd83d545b5da19113d723eeebcab1e77e2 (diff)
downloadchef-720f3331f794a2ad31bee2b1113ac99fada85389.tar.gz
Merge remote-tracking branch 'origin/master' into chef_handler
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md88
1 files changed, 1 insertions, 87 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 049640d7ab..93a759ba88 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -1,87 +1 @@
-# Chef Client Release Notes 12.4.0:
-
-## Knife Key Management Commands for Users and Clients
-
-`knife user` and `knife client` now have a suite of subcommands that live under
-the `key` subcommand. These subcommands allow you to list, show, create, delete
-and edit keys for a given user or client. They can be used to implement
-key rotation with multiple expiring keys for a single actor or just
-for basic key management. See `knife user key` and `knife client key`
-for a full list of subcommands and their usage.
-
-## System Loggers
-
-You can now have all Chef logs sent to a logging system of your choice.
-
-### Syslog Logger
-
-Syslog can be used by adding the following line to your chef config
-file:
-
-```ruby
-log_location Chef::Log::Syslog.new("chef-client", ::Syslog::LOG_DAEMON)
-```
-
-THis will write to the `daemon` facility with the originator set as
-`chef-client`.
-
-### Windows Event Logger
-
-The logger can be used by adding the following line to your chef config file:
-
-```ruby
-log_location Chef::Log::WinEvt.new
-```
-
-This will write to the Application log with the source set as Chef.
-
-## RemoteFile resource supports UNC paths on Windows
-
-You can now use UNC paths with `remote_file` on Windows machines. For
-example, you can get `Foo.tar.gz` off of `fooshare` on `foohost` using
-the following resource:
-
-```ruby
-remote_file 'C:\Foo.tar.gz' do
- source "\\\\foohost\\fooshare\\Foo.tar.gz"
-end
-```
-
-## WindowsPackage resource supports URLs
-
-The `windows_package` resource now allows specifying URLs for the source
-attribute. For example, you could install 7zip with the following resource:
-
-```ruby
-windows_package '7zip' do
- source "http://www.7-zip.org/a/7z938-x64.msi"
-end
-```
-
-Internally, this is done by using a `remote_file` resource to download the
-contents at the specified url. If needed, you can modify the attributes of
-the `remote_file` resource using the `remote_file_attributes` attribute.
-The `remote_file_attributes` accepts a hash of attributes that will be set
-on the underlying remote_file. For example, the checksum of the contents can
-be verified using
-
-```ruby
-windows_package '7zip' do
- source "http://www.7-zip.org/a/7z938-x64.msi"
- remote_file_attributes {
- :path => "C:\\7zip.msi",
- :checksum => '7c8e873991c82ad9cfcdbdf45254ea6101e9a645e12977dcd518979e50fdedf3'
- }
-end
-```
-
-To make the transition easier from the Windows cookbook, `windows_package` also
-accepts the `checksum` attribute, and the previous resource could be rewritten
-as:
-
-```ruby
-windows_package '7zip' do
- source "http://www.7-zip.org/a/7z938-x64.msi"
- checksum '7c8e873991c82ad9cfcdbdf45254ea6101e9a645e12977dcd518979e50fdedf3'
-end
-```
+# Chef Client Release Notes 12.5.0: