more flexibility in user ids on rsync tasks
Description
Problem/Justification
Impact
SmartDraw Connector
Katalon Manual Tests (BETA)
Activity

Dru Lavigne June 6, 2019 at 2:14 PM
Also notes that it is in the field description in the Guide.

William Gryzbowski June 4, 2019 at 12:17 PM
Thanks for the feedback
Right now its in the field tooltip.
We may decide to split it into another field in the future, but no plans on working on that now.

George Kyriazis June 3, 2019 at 9:28 PM
You are right. I didn't realize that you can specify user@host for the remote host.
You can close, or you guys may decide to make it clearer in the documentation somewhere.
Thank you.

William Gryzbowski June 3, 2019 at 2:57 PM
You should be able to specify a custom remote user for rsync, does that not work?

George Kyriazis June 2, 2019 at 10:40 PM
Hmm, good point on ACLs.
Scenario described below, both with no ACLs, no domains:
A public NFS share with uid squashing (ie. all incoming traffic mapping to a single uid), rsync-ed to a remote Synology server under a different uid. This is for backup purposes, but we don't care about keeping uids, since all files are owned by the same uid.
A related case that we are not hitting, but it's a useful scenario to cover, I think: Directory (share) with multiple uids, again rsynced to a synology server. In order to transfer all files correctly, source uid needs to be root, so it can read all files despite permissions. However, synology does not have a root user. It has an "admin" user, which has admin access. I don't think you can create a user "root", though, since it will clash with the (internal) root user.
Details
Details
Assignee

Reporter

Currently, you can specify a userid for an rsync tasks, but the source and destination user ids must match.
Allow for the ability to specify different user ids for source and destination.