| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
* Chef-16 resource cleanup + unified_mode
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
this is using:
Layout/AlignArguments:
Enabled: true
EnforcedStyle: with_fixed_indentation
the default style can use really excessive whitespace. on starting
lines which are already long, it fully indents across to where the
arguments start and then begins the line there.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
This gives a speed boost since rubygems does not have to scan through
every gem in the gemset in order to find the file.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Mostly cleaning up how we describe name properties, but also copying over some edits that happened on the docs site.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Provide users with more helpful messages
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Just stick the descriptions on a single line so that we utilize large monitors.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Due to changes in chef-client 14 old cookbooks started winning and this causes lots of problems, especially for old incompatible resources. Chef client should always win here.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Not all of them, but a good chunk.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
From the docs site
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
If we want these to throw a no ops vs. a hard failure we need them to be
wide open. Since a lot of people (including all of chef-cookbooks) have
coded as if these will gracefully skip this would have been a breaking
change.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
apt-get is a link to yast2 in suse so these resources fire there when someone wouldn't expect them to. Looking back we probably should have skipped the whole platform based no-op thing, but that ship sailed. This makes it behave the way a user would expect it to. What happens if you have apt compiled on your gentoo box? Well it's going to break. We'll just have to live with fixing it for 99.99% of users instead of the current 95%. Also: This is faster.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Also allow the pin priority to be an integer since there's no reason that needs to be a string
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
The resource fails without these values. Let's require them to give the user a proper error message
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
Specs are a placeholder on the provider side
Signed-off-by: Tim Smith <tsmith@chef.io>
|