| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
| |
the previous specs didn't catch my error because they didn't
comprehensively test against both kinds of resources that might be
passed into the provider as the new_resource. this fixes that, but the
patch is ugly, but we're trying to ship 12.0.2 as a bugfix, so ugly
will have to stand for now.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
the apt provider attempts to check if it has a provider that
responds to :default_release (i.e. a real apt_package resource) via
if the provider attribute is explicitly set or not, which is relying
on a side-effect which broke in 12.0. the correct behavior is just
to duck-type the new_resource object and see if it
respond_to?(:default_release) and then use it if it does.
|
| | |
|
| |\ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Knife now gives an error message like this when an SSL error occurs:
```
ERROR: Could not establish a secure connection to the server.
Use `knife ssl check` to troubleshoot your SSL configuration.
If your Chef Server uses a self-signed certificate, you can use
`knife ssl fetch` to make knife trust the server's certificates.
Original Exception: OpenSSL::SSL::SSLError: SSL_connect returned=1
errno=0 state=SSLv3 read server certificate B: certificate verify failed
```
|
| |/ |
|
| |\
| |
| | |
Jdm/issue 2626 rebase
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |\ \
| |/
|/| |
Preserve relative paths in Link resource
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
need to support relative paths in its 'to' attribute since one can create a symlink pointing to a relative location. This is useful if the directory that symlink resides in moves to a different place (e.g. mounting a disk on a separate location).
This commit preserves relative paths inside the "encode_path" method used by the link operations and expands relative paths in similar fashion when being used by file operations.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This reverts commit 1241ea6f9866d0e61d11129bb32e5fc96cd2bac0, reversing
changes made to 34d956c6b96087e6ca4bfbc9080037ded481709d.
Conflicts:
spec/functional/resource/file_spec.rb
spec/functional/resource/link_spec.rb
spec/unit/provider/link_spec.rb
|
| |\ \
| | |
| | | |
Cleanup Mixin:ShellOut use/specs
|
| | | | |
|
| | | | |
|
| |/ / |
|
| |\ \
| |/
|/| |
Constrain version of database cookbook
|
| |/
|
|
|
|
|
|
|
|
|
| |
A release of mysql-chef_gem broke the database cookbook because
it removed the default recipe which the database cookbook was using.
Since the database cookbook did not lock versions of mysql-chef_gem,
it pulls the latest mysql-chef_gem cookbook and fails.
An update to the database cookbook was released to fix this, however
Berks dep solving is getting the latest mysql-chef_gem and an older database
cookbook for the webapp test cookbook.
|
| |\
| |
| | |
Fix attribute whitelisting
|
| | | |
|
| |/
|
|
| |
False-y values are still there.
|
| |
|
|
|
|
| |
The error message from OpenSSL when connecting to a non-ssl service is
confusing--it looks like a certificate validation failure. Catch the
error and explain what caused it.
|
| | |
|
| |\
| |
| | |
Resolve the circular dependency between ProviderResolver and Resource.
|
| | |
| |
| |
| | |
https://github.com/opscode/chef/pull/2610.
|
| |/ |
|
| |\
| |
| | |
Fix Digester to require its dependencies
|
| |/
|
|
|
|
|
|
| |
Without thus using rspec gets you:
```
uninitialized constant Chef::Digester::Singleton
```
|
| |\
| |
| | |
Fixes #2578, check that `installed` isn't empty
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| | |
The underlying issue in #2578 is when a formula is `keg_only`, but not
installed, we're sending `#last` to an empty Array, which returns
`nil`, and causes the `NoMethodError` reported in #2578 and in the
homebrew cookbook issue. This should also resolve that issue:
https://github.com/opscode-cookbooks/homebrew/issues/53
|
| |\ \
| |/
|/| |
Stub windows? check in the unit test to make sure specs are green on windows
|
| |/ |
|
| |\
| |
| | |
Fix issue where Windows::Constants could potentially not exist, causing win event log module to crash
|
| | |
| |
| |
| |
| |
| | |
event log module to crash
Fix for Issue #2560
|
| |\ \
| | |
| | | |
Fix windows service when :interval is set
|
| | | | |
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
windows service is enabled.
Make sure that we don't raise error when :interval is set with :client_fork if we are on windows.
|
| |\ \
| | |
| | | |
Restore compatibility with knife-windows
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| | |
Chef::Knife::Core::BootstrapContext
and uses the Chef 11 arity in its constructor (https://github.com/opscode/knife-windows/blob/master/lib/chef/knife/core/windows_bootstrap_context.rb#L36)
In order to protect compatibility with knife-windows make sure that we have a default
for the new parameter that is added to the BootstrapContext constructor.
|
| |\ \
| |/
|/| |
Restore path attribute in execute resource with deprecation warning
|
| | | |
|
| | |
| |
| |
| |
| |
| |
| |
| | |
execute resource. Even tough this attribute is not being honored by any
provider, some existing cookbooks are still depending on this attribute.
Restore path attribute in execute resource with a deprecation message
that it will be removed in Chef 13.
|
| |/ |
|
