delta/ruby-gems/chef.git/lib/chef/knife.rb, branch https

Convert to default_paths API

2020-07-23T00:24:48+00:00

Signed-off-by: Lamont Granquist

Use .match? not =~ when match values aren't necessary

2020-06-11T22:32:53+00:00

Autocorrected from RuboCop Performance which is now smart enough to detect when you use the match and when you don't. Using match? does not create any objects so it's slightly faster and uses less memory.

Signed-off-by: Tim Smith

Get lib/ free of spelling violations.

2020-05-19T03:29:40+00:00

Signed-off-by: Pete Higgins

Knife bootstrap options cleanup

2020-04-17T17:20:31+00:00

We have issue that are caused by old code before merging of hash values
were done correctly.

The `config` hash correctly merges all options and should always be
used.

Knife plugins should never touch Chef::Config[:knife] values (either
reading or writing from them).

The `knife_config` should be converted to the `config` hash since it
directly accesses Chef::Config[:knife] values.

The `config_value()` helper should no longer be used.  Very clearly most
people started to use that when they should just use the config hash
directly.  That was intended to be used only when a knife cli option
was being renamed and the former configuration value needed to be
used as well.  It has been cargo culted around as the way to access
config values, and that should really stop.

The DataBagSecretOption mixin has been cleaned up so that the cli
options read+write only to the config[:cl_secret] and
config[:cl_secret_file] values.  The config file values go into
config[:secret] and config[:secret_file].  The fact that those are
the merged values in the `config` hash doesn't matter since only
the cli should be writing to the first two and only the config
file should be writing to the latter two.  I don't know why it was
made so complicated to begin with, but if there's some hidden
chef-11.early backcompat there, then chef-16 deliberately breaks that.

The use of `locate_config_value` helpers in all knife plugins is also
discouraged (but they all implement those themselves), just use the
config hash, which has the correct hash merge ordering.  All of those
need to be deleted.

Signed-off-by: Lamont Granquist

Remove copyright dates

2020-04-13T22:47:17+00:00

Legally incredibly dubious, particularly since we don't follow it
strictly as policy, and we have git history instead, which does it right.
This is just a waste of time and a cargo cult.

Signed-off-by: Lamont Granquist

Fix typo

2020-04-06T17:16:26+00:00

Signed-off-by: Vivek Singh

Update all our links to use the new docs site format

2020-03-04T23:51:57+00:00

When we migrated to hugo the URLs changed a bit. Nothing ends in .html and we moved all the resources into their own dir.

Signed-off-by: Tim Smith

Move knife-acl gem commands into chef in their own namespaces

2020-01-29T20:24:52+00:00

Ship these knife commands so we can kill off knife-acl, but move them under their own namespaces.

Signed-off-by: Tim Smith

Remove DK wording from knife warning

2020-01-28T19:01:58+00:00

We won't have a DK when we have Chef 16 so this shouldn't be there.

Signed-off-by: Tim Smith

Add chef-utils gem with various recipe DSL helpers

2019-11-08T22:06:33+00:00

This is the implementation of [RFC-087](https://github.com/chef-boneyard/chef-rfc/blob/master/rfc087-distro-sugar-helpers.md)
although some of the specifics have been iterated on and changed.

The documentation will be in the [README.md](https://github.com/chef/chef/tree/master/chef-utils/README.md) once this is merged.

While this PR mostly moves chef-sugar utilities into core-chef via this chef-utils gem, the scope of the chef-utils gem
should be considered larger than just that. As an example this PR moves the Mash class into this gem for reuse in ohai
as well.

Signed-off-by: Lamont Granquist