| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| | |
Fix a typo in the apt_repository spec
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \
| | |
| | | |
Use property vs. attribute in yum_repository
|
| |/
| |
| |
| |
| |
| | |
We just auto replace the attribute call with a property call here. We might as well use the right one to start with.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
|
|\ \
| | |
| | | |
Address test failures in SUSE 11.4 and 12.1
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The expected behavior of chef, as defined by our tests, is that if a
user specified in a group resource does not exist than chef should raise
an error. On suse, we use groupmod which will not raise an error if you
attempt to add a non-existent user to a group. This change adds in a
simple check that will raise an error if the specified does not exist.
Signed-off-by: Tom Duffield <tom@chef.io>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The `usermod` binary in SUSE 12.1 no longer throws an error if you
attempt to unlock a user account that has no password.
Signed-off-by: Tom Duffield <tom@chef.io>
|
| | | |
|
|\ \ \
| | | |
| | | | |
fixes for rubocop 0.44.1 engine
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
a few cops we have enabled got a little more accurate/stricter
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Attributes: add tests for regression in 12.0 fixed recently
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Tests for the issue that led up to
https://github.com/chef/chef/issues/5447
The Hash tests actually pass against 12.13.37 so it appearly that
only broke the Immutable array objects in 12.0. This both explains
why we didn't have any existing tests that caught it, and why it went
uncaught for so long. It also adds some ammunition to the argument
that fixing this in 12.14.x was not a major breaking change to users
that had been relying on the buggy 12.0 behavior.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
|\ \ \
| |/ /
|/| | |
convert svn_password to property + make sensitive
|
| | |
| | |
| | |
| | |
| | |
| | | |
should property-ize the rest of this as well
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Cron Provider: Eliminate crontab rewrite that happens with every chef-client run
|
| | |
| | |
| | |
| | | |
Signed-off-by: Peter Walz <pnw@umn.edu>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes a side effect of #5127 where if a `cron` resource sets MAILTO, PATH,
SHELL, or HOME, it gets updated with every chef-client run.
Signed-off-by: Peter Walz <pnw@umn.edu>
|
| | | |
|
|\ \ \
| | | |
| | | | |
Update EC2 tags for internal standards compliance.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
[ci skip]
Signed-off-by: Ryan Hass <rhass@chef.io>
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
[Knife] Fix deprecation warning when creating data bag items
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Fixes chef/chef-vault#215
Signed-off-by: Thom May <thom@may.lt>
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
remove dependency on Chef.run_context global state
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |/ / /
| |/| | |
| | | | |
| | | | |
| | | | |
| | | | | |
introduce run_context.root_run_context that avoids global state
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Bump omnibus deps once more.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Signed-off-by: Ryan Hass <rhass@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>
|
| | | | | |
|
|\ \ \ \ \
| |/ / / /
|/| | | | |
Update omnibus Gemfile.lock
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Update Gemfile.lock for omnibus to pull in latest OpenSSL 1.0.1 version.
Relates to internal issue COOL-595.
Signed-off-by: Ryan Hass <rhass@chef.io>
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
update openssl to 1.0.2j to address vulnerabilities
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Thiago Oliveira <thiagoo@yahoo-inc.com>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Thiago Oliveira <thiagoo@yahoo-inc.com>
|
| | | | |
|
|\ \ \ \
| |_|/ /
|/| | | |
Rebuild HTTP headers on each retried request
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Depending on how you configure your Chef client, it's possible that a
later retry would have an authentication timestamp header
(`X-OPS-TIMESTAMP`) that was more than 900 seconds old. Since the Chef
server treats timestamps older than this threshold as unauthorized
requests, you would potentially get seemingly spurious "401
Unauthorized" responses from the server.
A solution is to generate the headers on each retry so that we have a
new authentication timestamp for each retried request.
Signed-off-by: Shane da Silva <shane@dasilva.io>
|
| | | | |
|
|\ \ \ \
| |/ / /
|/| | | |
require the event_dispatch dsl since it's used in chef_class
|