| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
General cleanup
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Add a few more YARD comments to resources
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
I try to add them as I read through resources
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
|
| |
Added a todo to fix this when Ruby 2.3 support goes away since it's 3x
faster
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
RuntimeError
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Why is this not just in the duration calculator? Well we use it in two places and I would have had to add the same logic in both of those places. It's nice and easy to read this way
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>
|
|
|
|
|
|
| |
Also set the default the right way with execution_time_limit
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
Specify exactly what we're checking for in the error. This needs to go into the docs site as well.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
These are properties not attributes.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Nathan Williams <nath.e.will@gmail.com>
|
|\
| |
| | |
Deprecate the deploy resource and family
|
| |
| |
| |
| | |
Signed-off-by: Noah Kantrowitz <noah@coderanger.net>
|
|\ \
| | |
| | |
| | |
| | | |
chef/ash/add_none_frequency_to_windows_task_resource
Windows: Added :none frequency to windows_task resource
|
| | |
| | |
| | |
| | | |
Signed-off-by: NAshwini <ashwini.nehate@msystechnologies.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the shell_out approach to parse the version string from rpm is a bit of
a failed experiment.
the shell_out that gets incurred on every package provider is a bit
terrible for performance.
DNF < 1.00 has also never formally landed in any distribution and its
very difficult at this point to deploy it.
when amazon deploys DNF we should add a version comparison for that.
If this patch causes issues we can go back to adding some form of
`provides :package ... { which("dnf" }`
That will be much faster than having the shell_out().
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Eike Waldt <waldt@b1-systems.de>
|
|\ \ \
| |_|/
|/| | |
dnf_resource: be more specific for rhel packages
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
With #6351 and #6377, the DNF package provider was fixed to use yum by
default on RHEL 7, but the resource was still calling the DNF provider
if it happened to be installed.
We want to use the default of yum for RHEL 7, and only use DNF if we
call `set_priority_map` directly.
Signed-off-by: Naomi Reeves <naomi.c.reeves@gmail.com>
Resolves: Unexpectedly switching package managers
|
|/ /
| |
| |
| |
| |
| | |
Also fix the cookbook_file lookup logic missing a method it needed for file based keys
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Dmitry Shestoperov <dmitry@shestoperov.info>
|
| |
| |
| |
| | |
Signed-off-by: Dmitry Shestoperov <dmitry@shestoperov.info>
|
| |
| |
| |
| |
| |
| | |
metalink shipped in Fedora 10. I'm not sure about throttle as it doesn't google well, but there's references to it going back 5 years at least.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
| |
If we want these to throw a no ops vs. a hard failure we need them to be
wide open. Since a lot of people (including all of chef-cookbooks) have
coded as if these will gracefully skip this would have been a breaking
change.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
apt-get is a link to yast2 in suse so these resources fire there when someone wouldn't expect them to. Looking back we probably should have skipped the whole platform based no-op thing, but that ship sailed. This makes it behave the way a user would expect it to. What happens if you have apt compiled on your gentoo box? Well it's going to break. We'll just have to live with fixing it for 99.99% of users instead of the current 95%. Also: This is faster.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tom Doherty <tom.doherty@fixnetix.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the
best of my knowledge, is covered under an appropriate open
source license and I have the right under that license to
submit that work with modifications, whether created in whole
or in part by me, under the same open source license (unless
I am permitted to submit under a different license), as
Indicated in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
it.
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including
all personal information I submit with it, including my
sign-off) is maintained indefinitely and may be redistributed
consistent with this project or the open source license(s)
involved.
Signed-off-by: Tom Doherty <tom.doherty@fixnetix.com>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@msystechnologies.com>
|
|
|
|
|
| |
Conflicts:
spec/support/shared/functional/execute_resource.rb
|
|
|
|
| |
Signed-off-by: Gavin Reynolds <g.reynolds@src.gla.ac.uk>
|
|
|
|
| |
Signed-off-by: Gavin Reynolds <g.reynolds@src.gla.ac.uk>
|
|
|
|
|
|
| |
Without this anything that's gpg signed will fail waiting for the user to accept or deny the key. If users don't want this I've provided a new property to disable it.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@clogeny.com>
|
|
|
|
| |
Signed-off-by: nimisha <nimisha.sharad@clogeny.com>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|