summaryrefslogtreecommitdiff
path: root/RELEASE_NOTES.md
diff options
context:
space:
mode:
authorNoah Kantrowitz <noah@coderanger.net>2017-04-03 22:19:03 -0500
committerNoah Kantrowitz <noah@coderanger.net>2017-04-03 22:19:03 -0500
commit069757e39239f0516d9335c75794ca376c324717 (patch)
tree56b7583a5ec1b58ab1bdf2380be3644a90ef0552 /RELEASE_NOTES.md
parentc70408df1a90a875c6297edabacab115d74a2d9d (diff)
downloadchef-069757e39239f0516d9335c75794ca376c324717.tar.gz
Release notes, but I don’t love them. [ci skip]
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
Diffstat (limited to 'RELEASE_NOTES.md')
-rw-r--r--RELEASE_NOTES.md14
1 files changed, 14 insertions, 0 deletions
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
index b1e33fbc9f..67f54644a8 100644
--- a/RELEASE_NOTES.md
+++ b/RELEASE_NOTES.md
@@ -193,3 +193,17 @@ This will also affect nokogiri, but that gem natively supports UTF-8, UTF-16LE/B
who really need to write something like Shift-JIS inside of XML will need to either maintain their own nokogiri installs or will need to
convert to using UTF-8.
+### DSL-based custom resources and providers no longer get module constants
+
+Up until now, creating a `mycook/resources/thing.rb` would create a `Chef::Resources::MycookThing` name to access the resource class object.
+This const is no longer created for resources and providers. You can access resource classes through the resolver API like:
+
+```ruby
+Chef::Resource.resource_for_node(:mycook_thing, node)
+```
+
+Accessing a provider class is a bit more complex, as you need a resource against which to run a resolution like so:
+
+```ruby
+Chef::ProviderResolver.new(node, find_resource!("mycook_thing[name]"), :nothing).resolve
+```