| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
this is part of our informal style guide, lets make it formal since
clearly its not getting followed very well.
|
|
|
|
|
|
|
|
| |
lets us use Gem::Dependency constraints directly as rspec
constraints for matching Chef::Version and RUBY_VERSION.
copies some magic sauce from bundler that does something
similar
|
|
|
|
|
|
|
|
|
| |
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"
|
|
|
| |
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"
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Rerunning ohai wastes a lot of time. This should
get us back to within our time limits in appveyor
even with the perf regression in Ohai.
Don't rerun ohai for unit/regsitry_helper_spec
Ohai is slow. We don't need to rerun this, it's
already run in our spec_helper.
Don't keep rerunning ohai for reboot_pending_spec
Running Ohai is slow. This should know almost 2
mins off the runtime of the tests.
Don't need to run ohai for registry_spec
crypto_spec does not need its own ohai
cmdlet_spec does not need its own ohai
functional registry_helper_spec does not need its own ohai
Use spec ohai system for knife configure_spec
Use OHAI_SYSTEM for dsc_script_spec
use OHAI_SYSTEM for dsc_resource_spec
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
aes-256-cbc does not seem to work when openssl is in fips mode.
The only other reference I could find to this was:
https://access.redhat.com/solutions/176633
|
|
|
|
|
|
| |
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.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
- multipackages dpkg_package
- fixes edge conditions in load-current-resource around purging/removing
packages that threw errors before
- fixes the ability to purge packages that have been removed
- adds a lot of functional tests for dpkg_package
|
| |
|
| |
|
|\
| |
| | |
Use -Command flag on Nano
|
| | |
|
| | |
|
| | |
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
although appveyor does, so must have cygwin?
|
|\
| |
| | |
#3266 Fix bad Windows securable_resource functional spec assumptions for default file owners/groups
|
| | |
|
| | |
|
|/ |
|
|\
| |
| | |
Chef-DK nightlies on debian and el6 have been failing on these timing-based tests, doing a quick fix
|
| |
| |
| |
| | |
out why it fails
|
| | |
|
|/ |
|
|
|
|
|
|
| |
* Share specific recipes code to application parent
* Update specs to passing, update specs to RSpec 3.
* Specs for set_specific_recipes, solo, client.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
The registry_spec has been broken since we switched to rspec 3
:pending was running the tests, but expecting them to fail. There
seems to be a bug where if there is a failure outside the test,
in our case the before block was silently raising an exception
accessing resource_name, the tests would fail as expected but
rspec would return with an exit code of 1
|
|
|
|
|
|
|
|
|
|
|
| |
- Warning on incorrect usage of the command resource in any script
resource
- Warning on code in script resource being nil
- Specs added to force deprecation of incorrect usage in Chef-13
- Specs added around the (supported) incorrect usage in Chef-12
- Cleanup+Modernization of providers and specs
- Fixed some global state bugs around the Chef::Log.level in the spec
tests
|
| |
|
|
|
|
| |
default
|
| |
|
|\
| |
| | |
aix service provider
|
| | |
|
| | |
|
|\ \ |
|
| |/
| |
| |
| |
| | |
Pushed the ARGV.clear statement required for the apply_spec
file up into a before(:suite).
|