| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If #5606 is approved, any resource that creates a property that is an
already-existing Ruby method on a Chef::Resource object will throw a
deprecation warning. The ohai resource currently creates a `name`
property which conflicts with the `name` property created in the base
Chef::Resource class.
This change updates the ohai resource and provider to the new style of
defining resources and stops overwriting the `name` method.
Signed-off-by: Adam Leff <adam@leff.co>
|
|
|
|
|
|
|
|
| |
Allows the usage of `action :unmount` to `umount` a mount point
Closes https://github.com/chef/chef/issues/5595
Signed-off-by: Grant Ridder <shortdudey123@gmail.com>
|
|\
| |
| | |
Core: fix Lint/UnifiedInteger cop
|
| |
| |
| |
| |
| |
| | |
believe this becomes necessary for ruby 2.4/3.0
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | | |
Core: Structure deprecations with additional metadata
|
| |/
| |
| |
| |
| |
| |
| |
| | |
This adds URLs to each class of deprecation, and correctly prints and
formats them for maximum user efficiency. We also provide the URL to the
data collector for Visibility to ingest.
Signed-off-by: Thom May <thom@chef.io>
|
|/
|
|
|
|
| |
Signed-off-by: NimishaS <nimisha.sharad@msystechnologies.com>
Signed-off-by: NimishaS <nimisha.sharad@msystechnologies.com>
|
|\
| |
| |
| |
| | |
MsysTechnologiesllc/dh/adding_powershell_package_manager_support
Adding support for Powershell package manager to Chef package provider
|
| |
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Thom May <thom@chef.io>
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
StartCalendarInterval has some gotchas so we coerce it to sanity check.
According to `man 5 launchd.plist`:
StartCalendarInterval [is a] <dictionary of integers or array of dictionaries of integers>
... Missing arguments are considered to be wildcard.
What the man page doesn't state, but what was observed (OSX 10.11.5, launchctrl v3.4.0) is that key that are specified, _but with invalid values, will also be silently treated as a wildcard values.
This means that an entry like:
{ "Hour"=>0, "Weekday"=>"6-7"}
will not just run on midnight of Sat and Sun, rather it will run _every_ midnight.
We check to make sure that the values are integers and not strings, adhering to the manpage documentation.
This also ensures that only keys that StartCalendarInterval supports will be passed.
This eliminates passing a key (like `:hour` or `'hour') and thinking it works when in reality launchd is just treating it as a wildcard.
NOTE: This is a "breaking" change in that: it will break existing cookbooks that are using the current docs: https://docs.chef.io/resource_launchd.html (See start_calendar_interval); however the generated plist doesn't appear to actually do what was intended anyway.
|
|
|
| |
Mac: Ensure that launchd limit_load_to_session_type is properly handled
|
|
|
|
|
|
|
|
|
|
|
|
| |
We 1/2 wired up the noop functionality, but specifying that we only provided the resource on Linux caused that code to never run.
This prevents this sort of error on non-Linux platforms:
```
Cannot find a resource for apt_update on windows version 6.3.9600
```
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
package locking for apt, yum and zypper
|
| | |
|
|\ \
| | |
| | | |
Fix copyrights and update a few more Opscode references to Chef
|
| | |
| | |
| | |
| | |
| | |
| | | |
I think this happened when we merged the Opscode and Chef copyrights
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>
|
| | |
| | |
| | |
| | |
| | |
| | | |
should property-ize the rest of this as well
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |/
|/|
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | | |
Set yum_repository gpgcheck default to true
|
| |/
| |
| |
| | |
Fixes https://github.com/chef/chef/issues/5397
|
|\ \
| | |
| | |
| | |
| | | |
MsysTechnologiesllc/ali/windows_registry_key_resource_delete_fix
Allow deletion of registry_key without the need for users to pass data key in values hash.
|
| |/
| |
| |
| |
| |
| | |
data key in values hash.
Signed-off-by: aliasgar16 <aliasgar.batterywala@msystechnologies.com>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Reverted changes
Adding resource and provider for cab file support
Added method identifying package version for installation and removal of package
Updated code to idetitfy installed version
refactored some code
Refactored code for parsing dism get package output
Fixed rubocop issue, working on specs
created spec files
Working on unit specs
Added unit specs and working on functional specs
Working on functional specs and fixed rubocop errors
Fixed failing unit test cases
Resolved rubucop style error
Removed functional specs
Fixed error and working on functional specs
Added missing functional spec file
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
| |
fix non-utf8 filename issues in the file provider (again)
|
|
|
|
|
|
| |
(This was always intended to be the case, and it's difficult
to do it yourself. We have been teaching people whyrun-safe
methods to make resources right alongside Custom Resources, as well.)
|
|\
| |
| | |
revert supports[:manage_home] behavior
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| | |
even though i violently disagree that this is correct behavior and we're
just going to break everyone in one massive go when we hit Chef 13.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| | |
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>
|
|\
| |
| | |
Add Hash type to launchd:keep_alive
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| | |
Fixes #4691. I hope.
|
|\ \
| | |
| | | |
Rewrite linux useradd provider
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/ /
| |
| |
| | |
Signed-off-by: Thom May <thom@may.lt>
|
| |
| |
| |
| |
| |
| |
| | |
This will hopefully catch errors like this:
myresource 'name' do
not_if { 'some command' }
end
|
|/
|
|
|
|
|
|
|
| |
split out the user provider into 1:1 resources.
fix the behavior of the linux user provider to implement
manage_home behavior correctly.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|\
| |
| | |
Fix #4949 and Avoid Errno::EBUSY on docker containers
|