| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
| |
I ran cookstyle against the resources and fixes a few minor issues:
- Remove the now default guard interpreter from a powershell_script
- Use our rdoc like header format everywhere
- Remove some duplicate copyrights
- Simplify a few platform case statements
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
since we use double quotes, be consistent everywhere.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
i like this one, gives visual priority to returns or raises that are
buried in the middle of things.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
| |
Stops the kernel from scanning through all the activated gems every time in order
to resolve names into pathnames.
See rubygems/rubygems#2762
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>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
|
| |
Co-Authored-By: jjustice6 <jjustice6@bloomberg.net>
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
|
|
| |
"solaris".
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
| |
Signed-off-by: Joshua Justice <jjustice6@bloomberg.net>
|
|
|
|
|
|
|
|
| |
We had a few places where we checked for legacy opensuse platforms. Chef 15 doesn't support this platform and you won't be able to find binaries via omnitruck. We might as well yank out a bit of provider logic.
Also for some reason usermod has logic in a method for suse, but the provider didn't support that.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
We removed hpux support from other parts of ohai / chef. This appears to be the last of it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This is only for the Windows group.
Signed-off-by: Kapil Chouhan <kapil.chouhan@msystechnologies.com>
|
|
|
|
|
|
|
| |
converts all usage to just shell_out() from the numerous helper
utilities that we've had previously.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Thom May <thom@chef.io>
|
|
|
|
|
|
|
|
|
|
| |
Use dscl search verb in gid_used?
`dscl` has a search verb which makes checking whether a gid is
currently used much easier than parsing string output of listing all
gids.
Signed-off-by: Sean Karlage <skarlage@fb.com>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
fix dscl group provider func breakage from #5673
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
i didn't fully grok the way the dscl providers were written and
only half fixed the group dscl provider, but later did a better
job fixing the user one.
fixes the breakage caught in the dscl group func tests.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
| |
- consistent use of shell_out_compact!
- remove more uses of run_command
- some other code cleanup
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Using `all?` will return `false` when the array is empty.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
|
|
|
|
|
|
| |
The expected behavior of chef, as defined by our tests, is that if a
user specified in a group resource does not exist than chef should raise
an error. On suse, we use groupmod which will not raise an error if you
attempt to add a non-existent user to a group. This change adds in a
simple check that will raise an error if the specified does not exist.
Signed-off-by: Tom Duffield <tom@chef.io>
|
|
|
|
| |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
|
|
|
|
|
|
|
| |
Action is an array. We need to check to see if create is in the action
array instead of checking to see if it's ";create" which it never will
be.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
|
| |
|
| |
|
|
|
|
| |
rework the set_members method so duplicates are avoided
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
252 Style/TrailingCommaInLiteral
84 Style/TrailingCommaInArguments
15 Style/SpaceAroundKeyword
--
351 Total
We already dealt with SpaceAroundKeyword under its old name
SpaceBeforeModifierKeyword, it looks like it got stricter about
spaces after keywords.
TrailingComma also got split, and it looks like the
TrailingCommaInArguments behavior is new?
|
| |
|
|
|
|
|
|
|
|
|
| |
Style/NegatedWhile
Style/ParenthesesAroundCondition
Style/WhileUntilDo
Style/WordArray
Performance/ReverseEach
Style/ColonMethodCall
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
4174 Style/SpaceInsideHashLiteralBraces
1860 Style/SpaceAroundOperators
1336 Style/SpaceInsideBlockBraces
1292 Style/AlignHash
997 Style/SpaceAfterComma
860 Style/SpaceAroundEqualsInParameterDefault
310 Style/EmptyLines
294 Style/IndentationConsistency
267 Style/TrailingWhitespace
238 Style/ExtraSpacing
212 Style/SpaceBeforeBlockBraces
166 Style/MultilineOperationIndentation
144 Style/TrailingBlankLines
120 Style/EmptyLineBetweenDefs
101 Style/IndentationWidth
82 Style/SpaceAroundBlockParameters
40 Style/EmptyLinesAroundMethodBody
29 Style/EmptyLinesAroundAccessModifier
1 Style/RescueEnsureAlignment
|
|
|
| |
Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"
|
|
|
| |
Created via git ls-files | xargs perl -pi -e "s/(Copyright.*?), Opscode(,)? Inc(\.)?/\\1, Chef Software Inc./gi"
|
|
|
| |
Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"
|
|
|
|
|
|
| |
See chef/chefstyle#11 for analysis and discussion. We select '{}' since
audit of our source code shows that is the most common, and that used to
be the dominant learning paradigm (e.g. in ruby 1.9 pickaxe book.
|
|
|
|
|
|
|
| |
This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.
|
|
|
|
| |
useless use of `"#{foo.to_s}"`
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was causing the
```
Chef::Resource::Group
group modify action
when there is a group
behaves like correct group management
when the users exist
when append is not set
when group already contains some users
should remove all existing users and only add the new users to the group
```
spec to fail. The test passes an array which gets modified which breaks the test.
|
| |
|