| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Deprecate creating properties whose names are already methods
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
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>
|
|/
|
|
|
|
|
|
|
| |
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>
|
|\
| |
| | |
Use property vs. attribute in yum_repository
|
| |
| |
| |
| |
| |
| | |
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>
|
|/
|
|
| |
Fixes https://github.com/chef/chef/issues/5397
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We weren't allowing the actual action to work. Oops
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
Signed-off-by: Thom May <thom@may.lt>
|