diff options
| author | John Keiser <john@johnkeiser.com> | 2015-05-13 13:38:41 -0700 |
|---|---|---|
| committer | John Keiser <john@johnkeiser.com> | 2015-05-13 13:43:15 -0700 |
| commit | 34638bf82798bdcf01c28fbde6ac68dd1949c301 (patch) | |
| tree | ba58fa54264d520f6d4b9ae201176f5727e462ad /DOC_CHANGES.md | |
| parent | b6336c9de74095cc087463d5c6a3b28aac44e688 (diff) | |
| download | chef-34638bf82798bdcf01c28fbde6ac68dd1949c301.tar.gz | |
Add Chef::ResourceResolver.resolvejk/missing_method_missing
Diffstat (limited to 'DOC_CHANGES.md')
| -rw-r--r-- | DOC_CHANGES.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/DOC_CHANGES.md b/DOC_CHANGES.md index 31ea79f3d9..b0a8e0aaaf 100644 --- a/DOC_CHANGES.md +++ b/DOC_CHANGES.md @@ -27,7 +27,7 @@ Users are encouraged to declare resources in their own namespaces instead of put Starting with Chef 12.4.0, accessing an LWRP class by name from the `Chef::Resource` namespace will trigger a deprecation warning message. This means that if your cookbook includes the LWRP `mycookbook/resources/myresource.rb`, you will no longer be able to extend or reference `Chef::Resource::MycookbookMyresource` in Ruby code. LWRP recipe DSL does not change: the LWRP will still be available to recipes as `mycookbook_myresource`. -You can still get the LWRP class by calling `Chef::Resource.resource_matching_short_name(:mycookbook_myresource)`. +You can still get the LWRP class by calling `Chef::ResourceResolver.resolve(:mycookbook_myresource)`. The primary aim here is clearing out the `Chef::Resource` namespace. |