| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
|
|
| |
Slowly we'll get them all.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
|
|
| |
These are not state attributes, but we're treating them like state attributes.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
|
|
| |
Don't require providers in the resources since we map these automatically. Also remove or simplify the platform restrictions in the provides lines in the resources. We're not really getting anything from these the way we wire up resources.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
|
|
|
| |
Not all of them, but a good chunk.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |\
| |
| | |
Modernize launchd resource
|
| | |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/
|
|
|
|
| |
From the docs site
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |\
| |
| | |
Launchd limit_load_to_session_type accepts Array or String
|
| | |
| |
| |
| | |
Signed-off-by: Gregory Batye <gbatye@fb.com>
|
| |\ \
| | |
| | | |
Adding restart action to launchd resource
|
| | |/
| |
| |
| |
| |
| |
| | |
At first we wanted only support native actions with the launchd
resource and launchd does not have the concept of restart. You would
unload and load. But not having a restart was causing more confusion to
people.
|
| |/
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
| |
believe this becomes necessary for ruby 2.4/3.0
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
| |
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
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
