| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
This was always a coding bug. The `command` property is only used
internally but is exposed for users to twiddle because script
subclasses execute. Thus this still violates Liskov Substitution and
this is not an is-a relationship where inheritance might be appropriate,
because the script resource should /use/ the execute resource and
not /be an/ execute resource.
The more you know...
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
|
| |
IMO this is what users really want. It looks like we never
really fixed it right though.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
|
|
|
|
|
|
|
|
|
| |
This requires pulling in master of several gems, bumps all
the other gems, plus pulls in new kitchen-appbundle-updater
which supports pulling master of ohai.
Note that kitchen-windows is disabled because it turns out
it was broken and red on 12.19 all along.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
Require chef/version when trying to read it
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
When a node is bootstrapped in FIPS mode and then tries to run a
chef-client run it gets the following error:
```
STDERR: /opt/chefdk/embedded/lib/ruby/gems/2.3.0/gems/chef-config-12.18.31/lib/chef-config/workstation_config_loader.rb:163:in `rescue in apply_config': You have an error in your config file /var/opt/delivery/workspace/.chef/knife.rb (ChefConfig::ConfigurationError)
NameError: uninitialized constant Chef
/var/opt/delivery/workspace/.chef/knife.rb:2:in `eval'
/var/opt/delivery/workspace/.chef/knife.rb:2:in `eval'
/var/opt/delivery/workspace/.chef/knife.rb:2:in `from_string'
```
Signed-off-by: tyler-ball <tyleraball@gmail.com>
|
| | | |
|
| |/
|
|
|
|
|
|
| |
This correctly deals with quotes and so on in package options.
Fixes #5836
Signed-off-by: Mark Harrison <mark@mivok.net>
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| | |
cleans up the remaining new/current_resource ivars in remaining provider code
|
| | |
| |
| |
| |
| |
| | |
switches from using ivars to accessors for getters
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |/ |
|
| | |
|
| |\
| |
| | |
coerce immutable arrays to normal arrays in the yum_package resource
|
| | |
| |
| |
| |
| |
| |
| | |
as noted in comments this works around bugginess in the yum
provider that require a major refactor to fix.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| | |
classes providing an API should include VersionedAPI, whilst the factory
class includes VersionedAPIFactory.
Signed-off-by: Thom May <thom@may.lt>
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
When we make a request to a chef server, we capture the minimum and
maximum support API versions and allow them to be queried.
We then provide some infrastructure for making decisions on which class
should be used, in a middleware-ish mechanism.
Signed-off-by: Thom May <thom@chef.io>
|
| |/ |
|
| | |
|
| |
|
|
|
|
| |
department of redundancy department
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- cleans up a lot of ivar usage
- converts most providers to shell_out_compact_timeout!
- almost deprecates a few APIs, but can't quite yet
- windows providers need mixlib-shellout to take an argv
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
|
| |\
| |
| | |
Require net-ssh-multi 1.2.1 and remove our monkeypatch
|
| | |
| |
| |
| |
| |
| | |
The fix was merged upstream and released in 1.2.1
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Signed-off-by: Tom Duffield <tom@chef.io>
|
| |/
|
|
| |
Signed-off-by: Tom Duffield <tom@chef.io>
|
| | |
|
| | |
|
| |\
| |
| | |
Sanitize UTF-8 data sent to Data Collector
|
| | |
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
Signed-off-by: Tom Duffield <tom@chef.io>
|
| | |
| |
| |
| |
| |
| | |
pretty sure Chef::HTTP already debug logs requests
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
biinari/fix/deprecated-chef-platform-methods-class-name
Fix chef_platform_methods deprecation class name
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Deprecation warnings for Chef::Platform methods introduced in #5631 were
logged as e.g. `"Class.set is deprecated"` instead of `"Chef::Platform.set is
deprecated"`
This gets correct class name for message and adds unit specs to cover
the expected deprecation messages.
Unfortunately for these specs, some of these methods use each other,
resulting in multiple warnings. I have put an expectation for each of
these to avoid masking any other deprecations.
Signed-off-by: Bill Ruddock <bill.ruddock@gmail.com>
|
