[provisioner/shell] it works

[ChrisLundquist]

This was mostly for me to learn about how provisioners work in modern test-kitchen.
It also might be a poor man's way to support puppet.

[fnichol]

Looks like I have a bit of logic to account for in Kitchen::Driver::SSHBase, will look

[ChrisLundquist]

When I wrote the above comment, I saw /Applications/Adium... uploaded to the VM, then saw this line. I could have easily over looked something. I just saw "#{nil}/*" and chalked it up to that.

[fnichol]

This is looking pretty good! In post-1.0.0 releases, there is a data_path option (defaulting to test/integration/<suite>/data/, test/integration/data/, or './data/) that will upload all contents to the instance, available at/tmp/kitchen/data` by default. this could be a way to get some test or provision-related code onto the remote host. I'm going to have a play with this--it's a nice gentle start into non-Chef provisioners 👍

[ChrisLundquist]

Hmm, I only see data_path in ChefBase

$ grep -r "data_path" lib/
lib//kitchen/provisioner/chef_base.rb:      default_config :data_path do |provisioner|
lib//kitchen/provisioner/chef_base.rb:        config[:data_path]

The config block uses provisioner.calculate_path('data')

In #291 I moved calculate_path to Base from ChefBase. It seemed like calculate_path did what you mentioned.

Yeah, using a calculate_path to find bootstrap.sh would be better. We can fix it up here and I can update the other PR as well if we conflict.

[ChrisLundquist]

This should implement the path lookup change you mentioned above.
I pulled a commit from my other PR to avoid merge conflicts.
TravisCI tests seem to be occasionally timing out on a cucumber spec.

[ChrisLundquist]

added in cc44abe

[fnichol]

For the benefit of others, @ChrisLundquist and I had a great chat tonight and combined the first commit in this PR with some work in #298 to make Kitchen::Provisioner::Base smarter and more general purpose.