| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
support V1.
|
|\
| |
| | |
multipackage dpkg_package and bonus fixes
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
- multipackages dpkg_package
- fixes edge conditions in load-current-resource around purging/removing
packages that threw errors before
- fixes the ability to purge packages that have been removed
- adds a lot of functional tests for dpkg_package
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
| |
- extract to its own mixin so it can be included without
method_missing and the rest of the resources DSL
- add ability to inject different run_context
- add ability to create_if_missing into the resource_collection
|
|
|
|
| |
Following a517fa8a we can't call `child` on cookbook subdirs.
|
|\
| |
| | |
Require ShellOut before Knife::SSH definition
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I ran into a NameError when trying to run https://github.com/matschaffer/knife-solo/blob/master/test/knife_bootstrap_test.rb#L14 that I think this should fix.
My suspicion is that under normal operation shell_out gets required via the application or platform. And prior to moving config into its own project it was being required in chef/config.rb
In my tests since I end up loading knife ssh directly without the surrounding application things don't work out.
I'll likely just add a line to my test helper for now but wanted to open this for comment or future improvement.
|
| |
| |
| |
| |
| | |
it violates our dont-violate-the-new-resource policy for a reason, but
is likely still buggy if the resource gets reused.
|
|\ \
| | |
| | | |
Prevent inspect on PsCredential from printing out plain text password
|
| | | |
|
| | | |
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes #3434
Introduces --ssh-identity-file which is more like the
other SSH arguments (they all begin with --ssh except
this one). Behavior is unchanged.
Migrates '-i' over with --ssh-identity-file
Retains --identity-file with a deprecation statement.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- :update and :install are now treated the same way and throw the
same exceptions
- :remove and :purge don't require the source at all, so don't do
any checking on that
- fix some convoluted side-effecty logic in load_current_resource
- load_current_resource now correctly gets the dpkg state on
:remove and :purge when the file does not exist (pretty sure
the old logic did not)
- fixed the FIXME about using en_US.UTF-8 (the default for shell_out!)
- just use shell_out! to throw exceptions
- clean up all the specs and remove all the instance vars from the code
|
|\ \
| | |
| | | |
Update dsc_resource to use verbose stream output
|
| | | |
|
|/ /
| |
| |
| |
| |
| | |
s/vlaue/value/
Obvious fix.
|
| |
| |
| |
| | |
a list of users or as invites
|
| |
| |
| |
| | |
so that callers can 404 when deleting a nonexistent path
|
| | |
|
| |
| |
| |
| | |
/organizations/NAME/users
|
| | |
|
| | |
|
|\ \
| | |
| | | |
Allow named_run_list to be loaded from config
|
| |/
| |
| |
| |
| | |
nil default in application/client.rb shadowed any value from config when executing chef-client (but not chef-shell -z)
default in config is set to nil at https://github.com/chef/chef/blob/b0dbe243d469cc36477ba8102b74a8456b6f276d/chef-config/lib/chef-config/config.rb#L363, so otherwise this change is a no-op
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* removes the mutation of the new_resource.version
* adds package_class_supports_arrays for multipackage providers
* cleans up the package resource initializer and sets the package_name
correctly through the accessor method.
By mutating new_resource.version we were destroying the original intent
of what the user was requesting. This is a bug that must be fixed.
Generally, subclasses will be able to get the correct information they
need through either the version argument they were passed in
install_package(name, version) instead, or through their
`#target_version_array` method. If this breaks anything then those
providers need bugfixes as well (since this is a change to an internal
API accessible only to subclassing, and there are backwards compatible
and correct ways to get the information, this is *not* a SemVer
violating change). See the fix I made to the OpenBSD provider to
preserve the same semantics, avoid using new_resource.version where it
was inappropriate, and make the code more symmetrical where before
substantially different looking code in install_package and
remove_package had exactly the same ultimate effect.
The package_class_supports_arrays 'DSL' for writing multipackage
providers coerces the arguments to the virtual methods (e.g.
install_package) into arrays, even if the user is only requesting a
single package install. This removes most of the `is_a?(Array)`
checks from the implementation subclasses.
The cleanup of the initializer is similarly necessary so that we can
use Chef 12.5 coercions to make the package_name and version arguments
accept string, but always be Arrays. This should eliminate the rest
of the need to write `is_a?(Array)` code all over the package provider
implementations.
|
| |
| |
| |
| | |
to be the cookbooks (see http://rspec.info/blog/2015/11/rspec-3-4-has-been-released/, Better Failure Source Detection, for more info)
|
|\ \
| | |
| | | |
Implement live streaming for execute resources
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
the logic is now:
if the resource is not sensitive, and if it's explicitly requested to be
streamed or if the log level is info or debug, then we'll consider
streaming it.
If we're configured to send the output to the events stream, we'll do
so.
Otherwise, if we're not daemonized and have a TTY, we'll go to STDOUT
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This brings live streaming of execute resource output to the
output formatters. It also adds a mechanism for checking to
see if an output formatter is in use through the event dispatch
system.
It adds a new configuration option, "always_stream_execute", which
does what it says on the tin.
|
|\ \ \
| | | |
| | | | |
Modify remote_file cache_control_data to use sha256 for its name
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We want to support a fips mode, and doing MD5 with fips mode enabled
is wrong/hard. In this case, the type of checksum does not
matter, so let's just use sha256 since fips mode will be happy
with that.
For cases where the cache control data exists, we update it
to provide a seamless upgrade.
|
|\ \ \ \
| | | | |
| | | | | |
Adding ksh resource for #3923
|
| | | | | |
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
package/solaris: Adds alias method for upgrade_package.
|
| | | | | |
| | | | | |
| | | | | | |
This follows the same convention that the [AIX package provider](https://github.com/johnbellone/chef/blob/master/lib/chef/provider/package/aix.rb#L122) has done and adds an alias_method.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Use the proper python interpretor for yum-dump.py on Fedora 21+
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fedora 21+ use dnf as the primary package manager. Lamont added code in
12.5 to allow for a yum compat mode. This doesn't entirely work though
as we need yum-dump.py to correctly run. We were parsing the shabang in
the yum binary to find the path to python. On a dnf system the yum
binary is a bash script though so we were trying to run yum-dump.py
using bash which obviously fails. I added a fallback method to use
python if the shebang parsing returns bash. With this in place AND the
yum package installed you can use the package resource on Fedora.
|
|\ \ \ \ \ \ \
| |_|_|_|_|_|/
|/| | | | | | |
Use the initializer to avoid NoMethodError on nil.include?
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This should avoid node tags not being initialized properly to an empty
Array.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
node.tags should never be nil, always an Array. node.tags == nil would
be a bug.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Rename the argument so as to not collide with the tags method.
|