| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Pull in misc docs / comment updates from master
|
| |
| |
| |
| |
| |
| | |
This just makes the diff easier
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
| | |
Pull in the latest net-ssh/net-sftp & remove the http2 dep in chef-telemetry
|
| |
| |
| |
| |
| |
| | |
This expands our SSH support and the telemetry update slims the package down slightly.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Fix rspec warning about `not_to raise_error` with a specific exception.
|
| |
| |
| |
| |
| |
| | |
WARNING: Using `expect { }.not_to raise_error(SpecificErrorClass)` risks false positives, since literally any other error would cause the expectation to pass, including those raised by Ruby (e.g. NoMethodError, NameError and ArgumentError), meaning the code you are intending to test may not even get reached. Instead consider using `expect { }.not_to raise_error` or `expect { }.to raise_error(DifferentSpecificErrorClass)`. This message can be suppressed by setting: `RSpec::Expectations.configuration.on_potential_false_positives = :nothing`. Called from /Users/pete/work/chef/spec/unit/resource_spec.rb:381:in `block (4 levels) in <top (required)>'.
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|/
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fix wrong unit test exposed by cleaning up rspec deprecations.
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Bump all deps to current
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Avoid having to fix the openssl deprecation that only impacts ruby 2.8+
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Bump InSpec to 4.20.10
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Use /etc/chef for bootstrapping instead of ChefConfig
|
| |
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump Ohai to 15.12 to support macOS Big Sur
|
| |/
| |
| |
| |
| |
| | |
Beta OS time!
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Add Windows 8 Tester
|
|/
|
|
| |
Signed-off-by: Christopher A. Snapp <csnapp@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fix snap_package bugs
|
| |
| |
| |
| |
| |
| | |
We don't want / need the whole commit, but we need this
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First and foremost this fixes the bug in which #8827 where
`snap_package` hangs forever.
See the comment in the code for the nitty-gritty details, but snap never
returns an EOF so you have to jump through GREAT hoops not to hang
forever.
UNLESS you want to use nonblock+read, but it takes MUCH longer:
```
[phil@ldt-hardwired ~]$ time /tmp/test.rb char
real 0m0.252s
user 0m0.207s
sys 0m0.044s
[phil@ldt-hardwired ~]$ time /tmp/test.rb select
real 0m5.244s
user 0m0.183s
sys 0m0.056s
```
That's just for doing `GET /v2/snaps/black`
Second, if you try to install a snap that doesn't exist on the `stable`
channel then Chef crashes with a `undefined method [] on nil`, so let's
check for that explicitly.
And a bunch of other fixes that were required to even install anything:
* prevent get_current_versions from returning `[nil]`
* don't try to 'update' when something is not yet installed
* don't try to install versions, install packages
* don't try to push ruby hashes into HTTP without JSONing them first
* when installing, install one at a time, it's the only API that accepts a channel
* options is an array, not a hash
NOTE... there's a lot of janky here. A lot. It's the minimalist stuff
from #9106 I could pull in, while also making the socket stuff not
painfully slow. That PR aims to support versions and lots of other and
should be fixed up and [eventually] merged... but in the meantime this
provider doesn't even come close to working and this at least gets
packages installing.
After this, I never want to touch snap again.
Signed-off-by: Phil Dibowitz <phil@ipom.com>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Silence exception output in threaded test.
|
|/
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Warn during bootstrapping when using validation keys
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We should highly encourage users to move to validatorless bootstrapping
1) It's more secure
2) It requires less admin work since there no validation key to pass
around or rotate
This also provides an improved message helping the user to move off the
old keys and fixes some bad formatting where the 2nd line was indented
about 40 columns.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
knife vault on windows 10 fails due to ERROR: Chef::Exceptions::InvalidDataBagPath
|
| | |
| | |
| | |
| | | |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
| |/
| |
| |
| | |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Let the user know what protocol we're using in knife bootstrap
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes it really clear that you're not using the right protocol when you're bootstrapping a Windows node:
```
❰tsmith❙~/dev/work/chef(git✱knife_password)❱✘≻ bundle exec knife bootstrap 172.16.1.233 -U ubuntu
Connecting to 172.16.1.233
```
becomes
```
❰tsmith❙~/dev/work/chef(git✱knife_password)❱✘≻ bundle exec knife bootstrap 172.16.1.233 -U ubuntu
Connecting to 172.16.1.233 using ssh
```
Signed-off-by: Tim Smith <tsmith@chef.io>
|