| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Kapil Chouhan <kapil.chouhan@msystechnologies.com>
|
|
|
|
|
|
| |
We're not actually running these coverage tests and even if we did they don't have high value since you can game the numbers without writing quality tests.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Remove deprecated Chef-10 constraint handling
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
handle_deprecated_constraints has been a work around since Chef 10
Remove old specs that checked that the metadata was transformed correctly
Signed-off-by: Daniel Webb <dan.webb@damacus.io>
|
| |
| |
| |
| | |
Signed-off-by: Ingo Becker <ingo@orgizm.net>
|
|\ \
| | |
| | |
| | |
| | | |
chef/Kapil/GitHub-2860_exception_raised_in_define_resource_requirements
git resource: Fix for exceptions raised in why-run mode
|
| | |
| | |
| | |
| | | |
Signed-off-by: Kapil Chouhan <kapil.chouhan@msystechnologies.com>
|
|\ \ \
| | | |
| | | | |
Add multipackage support to homebrew
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Tiny tweak to grab the first item so we actually get the hash back in the error handling.
Given:
```ruby
package %w{curl totally_junk_pkg} do
action :upgrade
end
```
```
* No candidate version available for totally_junk_pkg
================================================================================
Error executing action `upgrade` on resource 'homebrew_package[curl, totally_junk_pkg]'
================================================================================
Chef::Exceptions::Package
-------------------------
No candidate version available for totally_junk_pkg
```
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
All required properties are now required for all actions by default
even if the action does not reference the property.
In order to only make the property required for a subset of the
actions, specify them as an array of symbols to the required
options on the property.
```
property :whatever, String, required: %i{start stop}
action :start do
end
action :stop do
end
action :enable do
end
action :disable do
end
```
That property will be required for start+stop but not for
enable+disable.
There's an unaddressed edge case here where if you reference the
property in an action which was not specified that it will also
fail validation. That is correct behavior. We should probably
dig into how to warn the user that they must either remove the
reference to the property from that action or else to add the
action to the list of required actions on the property.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \ \ \
| | | | |
| | | | | |
Knife bootstrap options cleanup
|
| | |_|/
| |/| |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We have issue that are caused by old code before merging of hash values
were done correctly.
The `config` hash correctly merges all options and should always be
used.
Knife plugins should never touch Chef::Config[:knife] values (either
reading or writing from them).
The `knife_config` should be converted to the `config` hash since it
directly accesses Chef::Config[:knife] values.
The `config_value()` helper should no longer be used. Very clearly most
people started to use that when they should just use the config hash
directly. That was intended to be used only when a knife cli option
was being renamed and the former configuration value needed to be
used as well. It has been cargo culted around as the way to access
config values, and that should really stop.
The DataBagSecretOption mixin has been cleaned up so that the cli
options read+write only to the config[:cl_secret] and
config[:cl_secret_file] values. The config file values go into
config[:secret] and config[:secret_file]. The fact that those are
the merged values in the `config` hash doesn't matter since only
the cli should be writing to the first two and only the config
file should be writing to the latter two. I don't know why it was
made so complicated to begin with, but if there's some hidden
chef-11.early backcompat there, then chef-16 deliberately breaks that.
The use of `locate_config_value` helpers in all knife plugins is also
discouraged (but they all implement those themselves), just use the
config hash, which has the correct hash merge ordering. All of those
need to be deleted.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
I guess this is minimum viable testing to ensure this doesn't break in
the future.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | | |
| | | |
| | | |
| | | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/ /
|/| |
| | |
| | |
| | |
| | | |
Simplify this resource and squash some files
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \ \
| | | |
| | | | |
Add a warning to the end of the chef run for EOL releses
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Use 2006 as the base year. Chef 15 goes EOL next year on 5-1-2021 so
2006 + 15 = 2021 and then we know it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/ /
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| | |
| | |
| | |
| | | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|/ /
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
| |
| |
| |
| |
| |
| |
| |
| | |
Legally incredibly dubious, particularly since we don't follow it
strictly as policy, and we have git history instead, which does it right.
This is just a waste of time and a cargo cult.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
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>
|
| |
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-Authored-By: pete higgins <pete@peterhiggins.org>
|
| |
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
Co-Authored-By: pete higgins <pete@peterhiggins.org>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a very useful base resource for mac systems that allows us to
write additional resources for managing macs. I've migrated their
library into the resource itself to make it a single self-contained
unit.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\ \
| | |
| | | |
Add resource partials
|
| |/
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\ \
| | |
| | | |
Add chef_client_systemd_timer resource
|
| | |
| | |
| | |
| | |
| | |
| | | |
It's a string now
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |/
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
| |
the bootstrap context isn't responsible for merging so this was always
testing the wrong behavior
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Spell checking in comments and log messages
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
|/
|
|
|
|
| |
This looks like it never worked but we happened to never run into it until we added a desktop platform to the pipeline.
Signed-off-by: Bryan McLellan <btm@loftninjas.org>
|