Skip to content
This repository has been archived by the owner on Jun 12, 2020. It is now read-only.

"Deploy cron script" task treats “dest” as a directory instead of as a file and fails #46

Closed
raneq opened this issue Mar 5, 2019 · 2 comments

Comments

@raneq
Copy link

raneq commented Mar 5, 2019

I suspect this will be a "works for me", but maybe you can help me out. I have posted a question to stack overflow

What ansible-restic should do here is to deploy a cron script based on a template, with name restic-backups-test, inside directory /etc/cron.d/ . However, it looks like ansible interprets that the directory should be /etc/cron.d/restic-backups-test and the file name just the epoch timestamp like 1551799877
I'm afraid it has to do with my environment instead, but I don't know what could make ansible change this behaviour, and my playbook doesn't do black magic.

@TheLastProject
Copy link
Collaborator

What's the value of your restic_repos variable?

@raneq
Copy link
Author

raneq commented Mar 5, 2019

I was wrong on the stackoverflow question, restic_repos contained a slash!!
Thank you a lot. If you want to take credit on stackoverflow, I will aprove your answer.
I don't know if it is usual to set variable names with special characters like that, in my case, was due a misunderstanding.

@raneq raneq closed this as completed Mar 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants