| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* changing the default drive for the config file to be the drive that the executable is launched from. This should allow for an easier launch of chef from a d: drive installation
Signed-off-by: John Kerry <john@kerryhouse.net>
* adding a check and a fallback to systemdrive for the base path when __FILE__ path doesn't have a drive (appears with linux hosts running windows targeted unit tests)
Signed-off-by: John Kerry <john@kerryhouse.net>
* fixing rubocop errors
Signed-off-by: John Kerry <john@kerryhouse.net>
* adding a __FILE__ path override for cache_path tests
Signed-off-by: John Kerry <john@kerryhouse.net>
|
| |
|
|
|
|
|
|
|
|
| |
Third-party data collector implementations are supported and may not
require a token for authentication. Therefore we must allow the case
where the token is nil in Chef Solo mode. To reduce the chance that the
data collector is accidentally enabled, only set the data collector URL
to a default value in Chef Client mode.
Signed-off-by: Daniel DeLeo <dan@chef.io>
|
| |
|
|
|
|
|
| |
Additionally, add info and debug logging for the auto-detection of
whether to enable the data collector.
Signed-off-by: Daniel DeLeo <dan@chef.io>
|
| |
|
|
| |
Signed-off-by: Daniel DeLeo <dan@chef.io>
|
| |
|
|
|
|
|
|
|
|
|
| |
The `--config-option` CLI option allows setting any `Chef::Config`
setting on the command line, which allows applications to be used
without a configuration file even if a desired config option does not
have a corresponding CLI option. This CLI option was present in the help
output for knife but was not actually implemented. Moving the behavior
into chef-config allows us to use it for both `chef-client` and `knife`.
Signed-off-by: Daniel DeLeo <dan@chef.io>
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
* Always use `*_proxy` environment variables.
* Make a `ChefConfig::Config.proxy_uri` method that gets used by
`Chef::Provider::RemoteFile::FTP` and `Chef::HTTP::BasicClient`.
* Remove `env` method from `Chef::HTTP::BasicClient` (using
`stub_const("ENV", ...)` in specs instead.)
* Remove `http_proxy_user` and `http_proxy_pass` methods from
`Chef::HTTP::BasicClient` (replaced by functionality in `ChefConfig`.)
|
| |
|
|
| |
Add tests around progress output and tidy up
|
| | |
|
| |
|
|
|
| |
This makes it the same as application/client.rb. This will let
the mixin be used the same way in both places.
|
| |
|
|
|
| |
This will behave similarly to the client.d directory.
The top-level ruby files will be loaded in sorted order.
|
| |
|
|
|
| |
This was testing `escape_glob` behavior.
Probably a copy-pasta mistake
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Backslashes should not be passed to Dir, as it does not work
when globbing in many cases.
Created new function that can be used with dir on windows.
`escape_glob_dir` should be used when the result is going
to be passed into Dir.
Fixes #4194
Replaces #4195
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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"
|
| |
|
|
|
| |
Allows you to run local mode with autodetected paths using native
policyfile objects only.
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
| |
Setting a value for `no_proxy` caused ruby to crash.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
the logic is now:
if the resource is not sensitive, and if it's explicitly requested to be
streamed or if the log level is info or debug, then we'll consider
streaming it.
If we're configured to send the output to the events stream, we'll do
so.
Otherwise, if we're not daemonized and have a TTY, we'll go to STDOUT
|
| |
|
|
|
|
|
|
|
|
| |
This brings live streaming of execute resource output to the
output formatters. It also adds a mechanism for checking to
see if an output formatter is in use through the event dispatch
system.
It adds a new configuration option, "always_stream_execute", which
does what it says on the tin.
|
| |
|
|
|
| |
Allows `knife` and such to parse config files with `chefdk.settting` in
them without error.
|
| |
|
|
|
|
|
|
|
|
| |
This resolves an issue where running `chef-client -c client.rb -z` will
attempt to create the local mode cache at the filesystem root with an
error like:
```
ERROR: Permission denied @ dir_s_mkdir - /local-mode-cache
```
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We keep seeing this randomly
```
1) Chef::WorkstationConfigLoader loading the config file when the config file exists and raises a ruby exception during evaluation raises a ConfigurationError
Failure/Error: expect { config_loader.load }.to raise_error(Chef::Exceptions::ConfigurationError)
expected Chef::Exceptions::ConfigurationError, got #<Errno::ENOENT: No such file or directory @ rb_sysopen - /tmp/Chef-WorkstationConfigLoader-rspec-test20150707-35300-f9yfb6> with backtrace:
# ./lib/chef/workstation_config_loader.rb:164:in `readlines'
# ./lib/chef/workstation_config_loader.rb:164:in `highlight_config_error'
# ./lib/chef/workstation_config_loader.rb:156:in `rescue in read_config'
# ./lib/chef/workstation_config_loader.rb:137:in `read_config'
# ./lib/chef/workstation_config_loader.rb:72:in `load'
# ./spec/unit/workstation_config_loader_spec.rb:275:in `block (6 levels) in <top (required)>'
# ./spec/unit/workstation_config_loader_spec.rb:275:in `block (5 levels) in <top (required)>'
# ./spec/unit/workstation_config_loader_spec.rb:275:in `block (5 levels) in <top (required)>'
```
I think the issue is that the tempfile gets GC'd, and when it gets GC'd, it deletes the file.
If it is cleaned up before it is used, then the test fails.
|
| | |
|
| |
|