From 9e5234e7ad55cdf4dee81d2cc1fbae4fcf4828d1 Mon Sep 17 00:00:00 2001 From: Baptiste Mille-Mathias Date: Tue, 28 Sep 2021 10:51:21 +0200 Subject: [PATCH] Remove reference to a bug in version 2.0.0 Seems too old and too specific to be useful nowadays --- plugins/modules/synchronize.py | 1 - 1 file changed, 1 deletion(-) diff --git a/plugins/modules/synchronize.py b/plugins/modules/synchronize.py index 5f63dd4..60101d5 100644 --- a/plugins/modules/synchronize.py +++ b/plugins/modules/synchronize.py @@ -197,7 +197,6 @@ notes: The user and permissions for the synchronize `src` are those of the user running the Ansible task on the local host (or the remote_user for a delegate_to host when delegate_to is used). - The user and permissions for the synchronize `dest` are those of the `remote_user` on the destination host or the `become_user` if `become=yes` is active. - - In Ansible 2.0 a bug in the synchronize module made become occur on the "local host". This was fixed in Ansible 2.0.1. - Currently, synchronize is limited to elevating permissions via passwordless sudo. This is because rsync itself is connecting to the remote machine and rsync doesn't give us a way to pass sudo credentials in. - Currently there are only a few connection types which support synchronize (ssh, paramiko, local, and docker) because a sync strategy has been