| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
Now that knife has been moved we can resolve the current warnings
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This moves knife into /knife, in the same way that chef-utils and
chef-config are separated.
NOTES:
== File History ==
If you see this message as the first message in the history of
an knife file, you can see the complete history by using
'git log --follow', 'git config log.follow true' to make it the default
behavior in this repository, or 'git config --globa log.follow true' to
make it the global default.
== API Changes ==
At the API level, there is one breaking change:
CookbookSiteStreamingUploader has been moved out of chef and into
knife/core.
There were a combination of reasons we chose this path:
- CookbookSiteStreamingUploader (CSSU) is only used within Knife.
- CookbookSiteStreamingUploader (CSSU) references the
command Chef::Knife::CookbookMetadata in order to generate
a metadata file for the cookbook to upload
- Chef::Knife::CookbookMetadata is no longer available to Chef:: because
Knife has been moved to its own gem. Knife gem depends on the Chef gem,
so Chef can't depend on something in Knife.
A search for usage in related projects (berks, chef-cli) and the
Internet at large shows that there are no known external consumers of CSSU.
For now, we'll move this class into Knife::Core, as it's going to be
faster than splitting off the metadata generation and time is a concern. If we
find that we need the metadata generation in chef/ proper, we should evaluate
decoupling that functionality from Knife::CookbookMetadata and exposing
it via something like `Chef::Cookbook::Metadata#from_cookbook_files`
== spec changes ==
The specs are kept in their existing locations, though we have
separated out a `knife_spec_helper` so that we can ensure knife is not
directly accessing chef requires; and chef is relying on knife's at all.
We also now clear gem paths with each test, to force gem state to reset.
This works around a problem where a combination of tests
is corrupting the internal Gem state, causing failures in
rubygems_spec. See branch `mp/broken-gems` for many more details around
findings so far.
Signed-off-by: Marc A. Paradise <marc.paradise@gmail.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
This reverts commit 182d83672e231c470e0b33ed777306a72a6bd76a.
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: snehaldwivedi <sdwivedi@msystechnologies.com>
|
|
|
|
|
|
| |
some garbage was getting output on stderr from the first block of tests
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
| |
using a proper instance_double avoids the errors and that's the right
thing to do here.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|\
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
| |
| |
| |
| | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| |
| |
| |
| | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|\ \
| | |
| | | |
Resolve Lint/ParenthesesAsGroupedExpression warnings
|
| | |
| | |
| | |
| | |
| | |
| | | |
Get some consistency here
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
| |
| |
| |
| | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
These came with one of the newer releases of Rubocop
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
There are some new spaces changes in RuboCop 1.4.2
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| |
| |
| | |
Just makes it a bit easier to read.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/
|
|
|
|
| |
We're working too hard here. No need for these.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
| |
This is a bit easier to read
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|\
| |
| | |
Avoid knife ssh freeze on windows
|
| |
| |
| |
| | |
Signed-off-by: dheerajd-msys <dheeraj.dubey@msystechnologies.com>
|
|/
|
|
|
|
| |
It is slow but it does catch real bugs
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
| |
Update some of these methods
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: Vivek Singh <vivek.singh@msystechnologies.com>
|
|
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Signed-off-by: Pete Higgins <pete@peterhiggins.org>
|
|
|
|
| |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Force subclasses to use the `config` hash directly.
This should not affect any knife plugins shipping in chef-workstation
since the calls to config_value have already been removed from all of
those plugins. The multiple-argument version of config_value was not
actually used anywhere in those plugins and the single value version
was removed and replaced with accessing the config hash. Since that
was introduced sometime in 15.x when the bootstrap changes went in,
it is not expected that many external knife plugins have picked up
the usage of config_value.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We should highly encourage users to move to validatorless bootstrapping
1) It's more secure
2) It requires less admin work since there no validation key to pass
around or rotate
This also provides an improved message helping the user to move off the
old keys and fixes some bad formatting where the 2nd line was indented
about 40 columns.
Signed-off-by: Tim Smith <tsmith@chef.io>
|