kitchen-sshtar expects directories, fails on hiera.yaml file (not a directory) about kitchen-puppet HOT 5 CLOSED

Does this fail with the normal transport, removing the sshtar transport?

from kitchen-puppet.

No, it does not.
Tried with kitchen-sync with sftp transport and classic scp and then it works without an error.

Seems like limitation of the kitchen-sshtar that it accepcts directories only.

But then I think kitchen-puppet should prepare all files in a single directory, and then process it - one transfer instead of separate operations for hiera, manifests and modules and anything else that I have not tried yet.

from kitchen-puppet.

Yeah that would definitely be a much faster operation than the multiple transfers that we are currently are performing. However, that would require user-end operations on the host system that test-kitchen is running. And I might see where that would be a concern for some users.

from kitchen-puppet.

I believe this is a matter for the driver not the provisioner.
i use my kitchen-ssh plugin. it supports ssh and sshgzip drivers. I use the sshgzip with cloud environments (AWS etc) and it is MUCH faster to send the repo once as a gzip file.
In AWS I use cloudformation to create my server before i use test-kitchen against it with driver kitchen-ssh using sshgzip driver.

from kitchen-puppet.

I'm going to close this. You can use the kitchen-shh with the sshgzip driver to get one file to copy to the server. Its quite valid for the provision to provide a set of files and directories to the driver to copy to the server. Its the drivers job to package them up into a gzip file or what and sent them to the server.

Closing....

from kitchen-puppet.