Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Downloads should allow wildcards in downloading files #1891

Open
pschaumburg opened this issue Apr 22, 2022 · 2 comments
Open

Downloads should allow wildcards in downloading files #1891

pschaumburg opened this issue Apr 22, 2022 · 2 comments

Comments

@pschaumburg
Copy link

🙍 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

    provisioner:
      downloads:
        /var/log/apache2/: './logfiles'

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.

@pschaumburg pschaumburg changed the title Downloads does not allow wildcards in downloading files Downloads should allow wildcards in downloading files Apr 22, 2022
@vkarve-chef
Copy link
Contributor

@pschaumburg just curious, did you try prefixing the wildcard with \ ? ref https://unix.stackexchange.com/questions/27419/how-to-use-wildcards-when-copying-with-scp
disclaimer: i haven't tried to repro the issue with a kitchen.yml entry as above in description.

@pschaumburg
Copy link
Author

@vkarve-chef
Tried all possibilities but nothing worked.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants