From ed86249ff2998d686e9b746f412a33437e56489c Mon Sep 17 00:00:00 2001 From: Lamont Granquist Date: Tue, 4 Apr 2017 11:34:29 -0700 Subject: add RELEASE_NOTES on gem_package source changes Signed-off-by: Lamont Granquist --- RELEASE_NOTES.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md index 75852adaf2..4a82994ff2 100644 --- a/RELEASE_NOTES.md +++ b/RELEASE_NOTES.md @@ -224,3 +224,17 @@ Accessing a provider class is a bit more complex, as you need a resource against ```ruby Chef::ProviderResolver.new(node, find_resource!("mycook_thing[name]"), :nothing).resolve ``` + +### Rubygems provider sources behavior changed. + +The default behavior of the `gem_package` and `chef_gem` resources is now to inherit whatever settings are in the external environment +that chef is running in. Chef no longer forces `https://rubygems.org`. The `Chef::Config[:rubygems_uri]` default has been changed to +nil. It can now be set to either a string URI or to an array of string URIs. The behavior of setting the source on an individual +resource now overrides the source setting completely and does not inherit the global setting. + +Users that previously relied on the source setting always being additive to "https://rubygmes.org" will find that they need to use +the array form and explicitly add "https://rubygems.org" to their resources. Users can now more easily remove "https://rubygems.org" +either globally or on a resource case-by-case basis. + +The behavior of the `clear_sources` property is now to only add `--clear-sources` and has no side effects on the source options. +>>>>>>> add RELEASE_NOTES on gem_package source changes -- cgit v1.2.1