The currently ruby requirement is going to break things when we pull
Ruby 3 into Chef Infra Client next year.
Signed-off-by: Tim Smith <tsmith@chef.io>
It looks like we're only using this in 3 test files and it conflicts
with new RuboCop releases, which is blocking us shipping that new
release in Chef Infra Client and Workstation
Signed-off-by: Tim Smith <tsmith@chef.io>
Fixes#5296
rspec 3.10.0 introduces text changes to test outputs. Let's keep it pinned - we don't need to keep rspec current.
Signed-off-by: James Stocks <jstocks@chef.io>
There are several outstanding issues about bumping faraday and
faraday_middleware. This gives us access to additional HTTP methods and
the versions we are pinned to are quite old.
Fixes#4234
Signed-off-by: Nick Schwaderer <nschwaderer@chef.io>
We're just deleting this from chef and workstation anyways. It's buried deep in the install directory and doesn't do anyone any good.
Signed-off-by: Tim Smith <tsmith@chef.io>
The `method_source` dependency for inspec-core has not been bumped in
five years, and it is indirectly holding `pry` back elsewhere in the
ecosystem which is causing issues for ruby 2.7+ support.
Signed-off-by: Nick Schwaderer <nschwaderer@chef.io>
+ inspec-core has all the real dependencies for inspec (the project).
+ inspec keeps all aws/azure/gcp code and their dependencies.
+ inspec depends on inspec-core and inspec-bin.
+ Removed test_files entirely.
+ Removed FNM_DOTMATCH on our globs... don't cargo cult.
+ Added some code to print out the gemspec and files to make it easier
to debug by executing the gemspec directly.
+ Sorted all deps... so hard to find things.
+ Added version specifiers where needed.
Signed-off-by: Ryan Davis <zenspider@chef.io>
First step is to get them agreeing on dependencies.
There's still some oddities between train vs train-core and
dependencies for AWS and the like, but this brings them in line so
diffing between them is MUCH better.
Next is to gut inspec and push everything over to inspec-core.
Signed-off-by: Ryan Davis <zenspider@chef.io>
Thor 1.0 drops support for Ruby 1.8 and 1.9. We should loosen this dep
to allow the 1.x series since bug fixes are occuring there now.
Signed-off-by: Tim Smith <tsmith@chef.io>
We'll be moving some code from chef-core to chef-telemetry and adding
that dependency in the next sprint.
Fixes#4716.
Fixes#4719.
Signed-off-by: Ryan Davis <zenspider@chef.io>
Ruby 2.3 is no longer supported. Drop this release from InSpec and
instead support the 3 latest Ruby releases.
Signed-off-by: Tim Smith <tsmith@chef.io>
One of the test files is causing chef omnibus failures on Solaris for some reason, but really there's no reason to ship all these test files in the install artifact. This slims down the gem and install size a good amount. I'm open to a better regex if someone has opinions.
Signed-off-by: Tim Smith <tsmith@chef.io>
By specifying a `max_redirects` attribute, the `http` resource worker
will follow any HTTP Redirect response (301, 302, etc...) up to the
limit defined by this attribute. For a local worker, exceeding that
limit will raise a `FaradayMiddleware::RedirectLimitReached` exception.
For a remote worker, the curl command will exit without populating the
`status` and `body` properties.
Signed-off-by: Keith Walters <keith.walters@cattywamp.us>
