blob: 5387870856a1677fbff044a8a92cb094aa41d6cc (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
|
# Chef Client Release Notes <unreleased>:
## 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
### Windows Event Logger
You can now have all Chef logs sent to the 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
```
|
