delta/ruby-gems/chef.git/spec/integration, branch https_shell

improve property-resource namespace collision exception

2016-10-31T22:45:21+00:00

Signed-off-by: Lamont Granquist

Update output assertion for environment set specs

2016-10-28T19:20:49+00:00

This test was originally written against a KnifeSupport that wasn't
actually pulling in the instance variables (i.e. :attribute) when
parsing the data. When running this command manually with Knife
v12.15.19, I get the output as now described in this test.

Signed-off-by: Tom Duffield

Add the `--field-separator` flag to knife show commands

2016-10-28T19:20:49+00:00

For the commands that allow you to filter which attributes it shows you
using the `--attribute` flag, add the `--field-separator` flag to allow
the user to customize which character(s) they want to use to deliniate the
attribute hierarchy.

```shell
knife node show NODE -S: -a "packages:Chef Client v12.12.15"
```

Signed-off-by: Tom Duffield

Return a raw hash when creating objects

2016-10-18T13:14:13+00:00

Fixes chef/chef-vault#215

Signed-off-by: Thom May

use delayed_action in accumulator spec

2016-10-11T17:48:00+00:00

Signed-off-by: Lamont Granquist

add some integration testing around accumulators

2016-10-11T00:17:20+00:00

probably also our best documentation on how to write accumulators right
now

Signed-off-by: Lamont Granquist

fix chef-solo spec timeouts (#5367)

2016-09-22T00:41:27+00:00

* fix chef-solo spec timeouts

caused by a race condition (not actually fixed) where the pid
can be read by the process which lost the race to lock it before the
pid has been written by the process which got the lock.

the result is a message like:

"WARN: Chef client  is running, will wait for it to finish and then run."

without any numerical pid.

i'm not super concerned with fixing the race, this will unbreak a lot
of red travis failures though.

Signed-off-by: Lamont Granquist 

* revert some debugging

Signed-off-by: Lamont Granquist

Make 12.5+ custom resources whyrun safe by default.

2016-09-16T21:27:27+00:00

(This was always intended to be the case, and it's difficult
to do it yourself. We have been teaching people whyrun-safe
methods to make resources right alongside Custom Resources, as well.)

Fix whitespace on EOMs

2016-09-16T21:12:32+00:00

use threads to workaround Process.spawn buginess

2016-09-02T20:42:02+00:00

there's a WONTFIX closed bug in ruby-lang.org on this bug:

https://bugs.ruby-lang.org/issues/10583

they seem to be favoring speed over accuracy with the result
that if you're doing I/O synchronization (like our run_lock?)
inside of a Process.spawn chain like this that you have to
wrap the spawn calls inside of threads.

probably a best practice to wrap every spawn call with a
Thread.

this probably also explains why we had the silly-long 20
second timeout?

Signed-off-by: Lamont Granquist