diff options
author | Tom Duffield <tom@chef.io> | 2017-03-15 14:14:42 -0500 |
---|---|---|
committer | Tom Duffield <tom@chef.io> | 2017-03-17 11:46:49 -0500 |
commit | 4b9fd225c8cc2fbc52e8965285f50d578c6d51ba (patch) | |
tree | ee625bfc3892eee69f3fde031baabf9ff8aad34a /RELEASE_NOTES.md | |
parent | b05a1fedf2993a26139e8ac8d0242c97e7c21351 (diff) | |
download | chef-4b9fd225c8cc2fbc52e8965285f50d578c6d51ba.tar.gz |
Update RELEASE_NOTES with chef-shell changes
Signed-off-by: Tom Duffield <tom@chef.io>
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r-- | RELEASE_NOTES.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 6ebd586b7b..88b4d64144 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -100,3 +100,8 @@ confusion. A simple example is `property :hash` which overrides the Object#hash is placed into the Chef::ResourceCollection which uses a Hash internally which expects to call Object#hash to get a unique id for the object. Attempting to create `property :action` would also override the Chef::Resource#action method which is unlikely to end well for the user. Overriding inherited properties is still supported. + +### `chef-shell` now supports solo and legacy solo modes + +Running `chef-shell -s` or `chef-shell --solo` will give you an experience consistent with `chef-solo`. `chef-shell --solo-legacy-mode` +will give you an experience consistent with `chef-solo --legacy-mode`. |