summaryrefslogtreecommitdiff
path: root/lib/chef/resource/yum_repository.rb
Commit message (Collapse)AuthorAgeFilesLines
* Add support for metalink and throttle in yum_repositoryyum_repoTim Smith2017-09-211-1/+4
| | | | | | metalink shipped in Fedora 10. I'm not sure about throttle as it doesn't google well, but there's references to it going back 5 years at least. Signed-off-by: Tim Smith <tsmith@chef.io>
* Sort yum repository options alphabeticallyTim Smith2017-09-211-8/+8
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Merge pull request #5606 from chef/adamleff/warn-on-dangerous-property-namesThom May2017-01-181-1/+0
|\ | | | | Deprecate creating properties whose names are already methods
| * Deprecate creating properties whose names are already methodsadamleff/warn-on-dangerous-property-namesAdam Leff2017-01-181-1/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When creating a resource, a user can create a property that is the same name as an already-existing Ruby method, such as `#hash`. In the case of the `#hash` method, this can cause issues when attempting to adding resources to other data structures, such as Arrays or Hashes. In other examples, this could cause unexpected behavior that is incredibly difficult to troubleshoot. This change adds a deprecation warning in the case where a user adds a property to a resource that the resource instance already responds to. If y'all are OK with this approach, I'll be happy to write up the deprecation doc for this for docs.chef.io. Signed-off-by: Adam Leff <adam@leff.co>
* | yum_repostiroy: Allow baseurl to be an array & allow fastestmirror_enabled falseupdate_yumTim Smith2017-01-051-1/+1
|/ | | | | | | | | Port two fixes that were made the yum cookbook yum_repository provider. https://github.com/chef-cookbooks/yum/pull/165 https://github.com/chef-cookbooks/yum/pull/162 Signed-off-by: Tim Smith <tsmith@chef.io>
* Merge pull request #5474 from tas50/yum_propertyLamont Granquist2016-10-211-1/+1
|\ | | | | Use property vs. attribute in yum_repository
| * Use property vs. attribute in yum_propertyTim Smith2016-10-191-1/+1
| | | | | | | | | | | | We just auto replace the attribute call with a property call here. We might as well use the right one to start with. Signed-off-by: Tim Smith <tsmith@chef.io>
* | Set yum_repository gpgcheck default to trueGrant Ridder2016-09-281-1/+1
|/ | | | Fixes https://github.com/chef/chef/issues/5397
* Fix makecache action name in yum_repositorymakecacheTim Smith2016-09-191-1/+1
| | | | | | | | | Our allowed action in the resource doesn't match the action name in the provider. makecache is the correct action not make_cache: https://github.com/chef-cookbooks/yum/blob/master/providers/repository.rb#L100 Signed-off-by: Tim Smith tsmith@chef.io
* Add back compatibility with old property namesTim Smith2016-09-141-2/+5
| | | | | | In yum 3.0 we changed the properties in the documentation, but never threw deprecation notices. Since there was no notice you would have no way to know to use the new properties. We need to add back compatibility with the old names and if we really want to kill them throw a proper deprecation warning. Signed-off-by: Tim Smith <tsmith@chef.io>
* More professional default nameTim Smith2016-09-141-1/+1
| | | | Signed-off-by: Tim Smith <tsmith@chef.io>
* Allow the :delete action for yum_repositoryTim Smith2016-09-141-1/+1
| | | | | | We weren't allowing the actual action to work. Oops Signed-off-by: Tim Smith <tsmith@chef.io>
* Create and delete yum repositoriesThom May2016-08-241-0/+76
Signed-off-by: Thom May <thom@may.lt>