| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Add deprecation warnings at the end of the run after the end of April 2021
|
| |
| |
| |
| |
| |
| |
| | |
There's no need to calculate it here since this code will only ever run
on 15
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| | |
Use 2006 as the base year. Chef 15 goes EOL next year on 5-1-2021 so
2006 + 15 = 2021 and then we know it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We really want to encourage people to upgrade. One way we can do this is
to just warn them that they're on an EOL release. This simple warning
might nudge them to upgrade their client. It's works off the base EOL
data of Chef 15 and takes the current release to add to that date. That
way we don't have to maintain anything and as long as we keep a yearly
release we're good. If we change the schedule then we either remove this
or update the logic. That's a risk in shipping code that doesn't fire
for 2 years.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Fix specifying sudo password in knife bootstrap
|
| | |
| | |
| | |
| | | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |/
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
|/
|
|
|
|
| |
I think we may finally have them all now.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fix knife bootstrap_version CLI option overriding config option
|
| |
| |
| |
| |
| |
| |
| |
| | |
closes #8834
@ccrebolder this should be all that is necessary to fix your issue.
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.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Spell checking in comments and log messages
|
| |
| |
| |
| | |
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>
|
|\ \
| | |
| | | |
Fixed systemd_unit not respecting sensitive property
|
| | |
| | |
| | |
| | | |
Signed-off-by: sanga17 <sausekar@msystechnologies.com>
|
| |/
| |
| |
| | |
Signed-off-by: sanga17 <sausekar@msystechnologies.com>
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|
|
|
|
|
| |
That's a breaking change we don't want to introduce.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
| |
I read the github review history wrong on this and totally missed this
suggestion.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Also add a pile of specs
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-Authored-By: pete higgins <pete@peterhiggins.org>
|
|
|
|
|
|
|
|
|
| |
The previous install logic had some flaws:
1) It relied on pkgutils to determine if xcode was installed and that doesn't seem to be entirely reliable. I copied over the plist logic from the macos cookbook, which seems much more reliable
2) The previous :install action was actually an :upgrade action on Macs which was VERY slow since it required reaching out to Apple's update servers. This corrects that behavior with a new :upgrade action that applies to macOS systems
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Include a rubular link with what we're trying to match
Signed-off-by: Tim Smith <tsmith@chef.io>
|