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

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

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 Layout/EmptyLineAfterGuardClause

2019-07-02T22:09:07+00:00

i like this one, gives visual priority to returns or raises that are
buried in the middle of things.

Signed-off-by: Lamont Granquist

fix a bunch of weirdly mangled require lines

2019-05-09T00:15:15+00:00

Signed-off-by: Lamont Granquist

Convert require to require_relative

2019-05-09T00:03:26+00:00

This gives a speed boost since rubygems does not have to scan through
every gem in the gemset in order to find the file.

Signed-off-by: Lamont Granquist

change HTTPServerException to HTTPClientException for ruby 2.6

2019-01-03T18:53:48+00:00

includes backcompat for 2.5

Signed-off-by: Lamont Granquist

Verify data bag exists before trying to create it

2017-03-02T22:36:14+00:00

[ZD-12613]
There are users who want to customize permissions to prevent a group of
users from creating new data bags but want to allow the group of users
to create data bag items within an existing data bag.

If the user doesn't have permission to create data bags then the current
API request sequence will prevent the user from creating a data bag item
even if the data bag already exists.

This commit fixes the above problem by verifying (not trying to create)
if the data bag exist through a GET request, if it doesn't the it tries
to generate it, then it proceeds to create the data bag item.

Signed-off-by: Salim Afiune

Update all auth email address from opscode.com and getchef.com to chef.io.

2016-02-02T22:53:28+00:00

Generated via git ls-files | xargs perl -pi -e "s/(Author.*?<[^@]+@)(?:opscode\\.com|getchef\\.com)(>)/\\1chef.io\\2/gi"

2016-02-02T22:43:28+00:00

Generated via git ls-files | xargs perl -pi -e "s/[Cc]opyright (?:\([Cc]\) )?((?\!$(date +%Y))\\d{4})(-\\d{4})?([, ][ \d]+)*(,|(?= ))/Copyright \\1-$(date +%Y),/g"

Use double quotes by default

2016-01-14T14:08:03+00:00

This is an entirely mechanically generated (chefstyle -a) change, to go
along with chef/chefstyle#5 . We should pick something and use it
consistently, and my opinion is that double quotes are the appropriate
thing.