-
-
Notifications
You must be signed in to change notification settings - Fork 342
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
rsync_extra_opts should be array instead of string #225
Comments
Also see #121 |
And #82 |
Ok, old news then. At least for me the default rsync builds got broken. With Ansible versions before 2.3 this worked just fine and I got all the files in src directory on my servers. Once the ansible got updated to 2.3 the rsync deployment got broken and instead of having just src directory contentes on server I also got the top-level contents for some reason. After changing the ansistrano_rsync_extra_params to array the expected behavior returned. |
The current setup works for all Ansible versions, including 2.3.0 which we test in Travis as you can see |
Current setup doesn't work on 2.3.0 as expected. The problem can be seen with following steps by using the example directories my-app:
change deploy.yml to:
When ansistrano-deploy defaults/main.yml has 'ansistrano_rsync_extra_params: ""' I get following files on deployment dir:
when I use older ansible version or change the ansistrano_rsync_extra_params: to [] I get following:
So in addition to the files I wanted to deploy, all files from my sub-directory, now I also get all top-level contents as well which seems to be an error. |
Seems to be an Ansible problem, as reported in #227 Not much we can do I am afraid |
Hi,
Ansistrano incorrectly passes rsync_opts as string when array is expected.
This breaks rsync copying with ansible 2.3.0.
Simple fix was to pass it an array so change the defaults/main.yml:
-ansistrano_rsync_extra_params: ""
+ansistrano_rsync_extra_params: []
For more information:
http://docs.ansible.com/ansible/synchronize_module.html#options
ansible/ansible#23575
The text was updated successfully, but these errors were encountered: