summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authordanielsdeleo <dan@getchef.com>2014-03-14 09:26:42 -0700
committerdanielsdeleo <dan@getchef.com>2014-03-14 14:09:37 -0700
commitaa9585f2f7d214c667fcba4cbf61e7e8114484ab (patch)
tree7f6a4d001a4a2968527541ff3ddf998c6387a59f /RELEASE_NOTES.md
parentbecb0427f813f787fd492798f6c97de67fdd732c (diff)
downloadchef-aa9585f2f7d214c667fcba4cbf61e7e8114484ab.tar.gz
Update release notes for CHEF-4367
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md18
1 files changed, 18 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index 12077a92a0..0a34f5619e 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -8,6 +8,24 @@ Details about the thing that changed that needs to get included in the Release N
-->
# Chef Client Release Notes:
+#### Chef Solo Missing Dependency Improvments ([CHEF-4367](https://tickets.opscode.com/browse/CHEF-4367))
+
+Chef 11.0 introduced ordered evaluation of non-recipe files in
+cookbooks, based on the dependencies specified in your cookbooks'
+metadata. This was a huge improvement on the previous behavior for all
+chef users, but it also introduced a problem for chef-solo users:
+because of the way chef-solo works, it was possible to use
+`include_recipe` to load a recipe from a cookbook without specifying the
+dependency in the metadata. This would load the recipe without having
+evaluated the associated attributes, libraries, LWRPs, etc. in that
+recipe's cookbook, and the recipe would fail to load with errors that
+did not suggest the actual cause of the failure.
+
+We've added a check to `include_recipe` so that attempting to include a
+recipe which is not a dependency of any cookbook specified in the run
+list will now raise an error with a message describing the problem and
+solution.
+
#### reboot_pending?
We have added a ```reboot_pending?``` method to the recipe DSL. This method returns true or false if the operating system