You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have the need of downloading files from a specific directory. The files within that directory aren't statically named. So they could contain always dates and times that are different.
To download those files, we are currently using
This results always in a directory named ./logfiles/apache2 which contains all the files.
A wildcard letter does result in the message like SCP download failed for file or directory '/var/log/apache2/*', perhaps it does not exist?.
❔ Possible Solution
Add options to download files recursively.
⤴️ Describe alternatives you've considered
I've also tried this with lifecycles in post_converge etc., which are very uncomfortable.
Additionally it would also a possibility to converge a node, then running a script without test-kitchen and destroy the node right after.
The text was updated successfully, but these errors were encountered:
pschaumburg
changed the title
Downloads does not allow wildcards in downloading files
Downloads should allow wildcards in downloading files
Apr 22, 2022
🙍 Problem Statement
We have the need of downloading files from a specific directory. The files within that directory aren't statically named. So they could contain always dates and times that are different.
To download those files, we are currently using
This results always in a directory named
./logfiles/apache2
which contains all the files.A wildcard letter does result in the message like
SCP download failed for file or directory '/var/log/apache2/*', perhaps it does not exist?
.❔ Possible Solution
Add options to download files recursively.
I've also tried this with lifecycles in post_converge etc., which are very uncomfortable.
Additionally it would also a possibility to converge a node, then running a script without test-kitchen and destroy the node right after.
The text was updated successfully, but these errors were encountered: