| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
taking 24h to get results back is unsustainable
|
|
|
|
|
| |
Closes #4160
Closes #3848
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
dpkg provider cleanup
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
| |
- :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
|
| | |
|
|\ \
| | |
| | | |
Fix typo in comment
|
|/ /
| |
| |
| |
| |
| | |
s/vlaue/value/
Obvious fix.
|
|\ \
| |/
|/| |
Documentation update: add README.md links to join IRC channels
|
|/
|
|
| |
Per btm's suggestion and the conversation at today's Developers Meeting, add some links to easy ways to join IRC and view read-only channel logs.
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| | |
a list of users or as invites
|
| |
| |
| |
| | |
so that callers can 404 when deleting a nonexistent path
|
| | |
|
|/
|
|
| |
/organizations/NAME/users
|
|\
| |
| | |
reboot_action for dsc_resource and WMF 5 and Win 10 Threshold 2 Allow dsc_resource with the LCM enabled.
|
| | |
|
|/ |
|
|\
| |
| | |
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
|
|\ \
| | |
| | | |
Multipackage internal API improvements
|
| | | |
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* 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)
|
| | |
|
| |
| |
| |
| | |
(the --path bundle/vendor screws up our ability to run bundle install)
|
|\ \
| | |
| | | |
rspec 3.4.0 broke master
|
|/ /
| |
| |
| | |
pinning to 3.3.x as a temp fix
|
| | |
|
|\ \
| | |
| | | |
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.
|