| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Use include? to example strings when we don't need a regex
|
| |
| |
| |
| |
| |
| | |
There's no need for match? with regex here.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | | |
This one is pretty odd. We would grep the line to see if it includes katello-ca-consumer and then we'd check it again in ruby. Let's just do that work once now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Switch to shell_out
Use include? instead of a regex
Add some simple YARD
Memoize the rhsm registration check
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \
| |_|/
|/| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: mwrock <matt@mattwrock.com>
|
|/ /
| |
| |
| | |
Signed-off-by: mwrock <matt@mattwrock.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Fix invalid output_locations raise start_time error.
- Improve validate_output_locations!
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |/
|/|
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| |
| |
| | |
Resolve the issues that pete pointed out plus a few others
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
Only use launchd create action on the service itself. Enable will trigger restarts which we want to avoid since that will prematurely hang things
Make sure we disable the restarter plist as well if someone runs the disable action otherwise any manual plist work will turn the client back on
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
|
| |
Launchd doesn't have the concept of a reload aka restart. Instead to update a daemon config you have to unload it and then reload the new plist. That's usually fine (actually just like upstart), but not if Chef is trying to restart itself. Currently if you change the nice level or interval the client will unload its own config which kills the run and it never gets started back up. So to work around this we're going to install a launchd daemon that has a watcher on the chef-client daemon plist file. It's only job to to unload and reload the client. That way when the daemonized chef-client process updates the plist the restarter job will handle the restart. To ensure we're not in the middle of the next recipe we use a chef_sleep resource to sleep a bit post launchd update.
I also updated the resource to work better with cinc while I was in here.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I needed this for testing and it just sorta seems like something we
should support. Yes that means people may be using chef-apply with some
sort of init system, but if that's something they wanna do then why not
just let them roll with that. This just copies the option from the
base.rb file and it works fine for me locally.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| | |
Signed-off-by: Davin Taddeo <davin@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Signed-off-by: Lamont Granquist <lamont@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
While this behavior was fixed for attributes a long, long time ago it
turns out we don't use this deep_merge mixin for constructing the
deep merge of attribute precedence levels any more.
This bug however surfaces because we still use deep_merge to merge
json attributes into normal attributes. That means that it is not
possible to pass a nil / null value in through -j and have it override
a normal attribute which is pulled back in from the node object on
the chef-server.
So this fixes that behavior to be consistent with the behavior of
attributes that we've had for several years now.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Allow removing profiles in osx_profile on Big Sur
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Users may want to cleanup old profiles after upgrading a Catalina box to
Big Sur. We should allow for that. It's just installing new profiles
where we need to fail hard.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \ \
| |/ /
|/| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|