blocks|key|104726|text|文件模块不会复制远程系统上的文件。src参数仅在创建指向文件的符号链接时由文件模块使用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|104727|如果您想要在远程系统上完全移动/重命名文件，那么最好的方法是使用命令模块来调用相应的命令：|104728|-+name:+Move+foo+to+bar
++command:+mv+/path/to/foo+/path/to/bar|code-block|syntax|javascript|104729|如果你想变得更花哨，那么你可以首先使用stat模块来检查foo是否确实存在：|104730|-+name:+stat+foo
++stat:+path=/path/to/foo
++register:+foo_stat

-+name:+Move+foo+to+bar
++command:+mv+/path/to/foo+/path/to/bar
++when:+foo_stat.stat.exists|104731|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

The file module doesn't copy files on the remote system. The src parameter is only used by the file module when creating a symlink to a file.

If you want to move/rename a file entirely on a remote system then your best bet is to use the command module to just invoke the appropriate command:

<pre><code>- name: Move foo to bar
 command: mv /path/to/foo /path/to/bar
</code></pre>

If you want to get fancy then you could first use the stat module to check that foo actually exists:

<pre><code>- name: stat foo
 stat: path=/path/to/foo
 register: foo_stat

- name: Move foo to bar
 command: mv /path/to/foo /path/to/bar
 when: foo_stat.stat.exists
</code></pre>

blocks|key|104765|text|我发现命令模块中的创建选项很有用。这样如何：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|104766|-+name:+Move+foo+to+bar
++command:+creates="path/to/bar"+mv+/path/to/foo+/path/to/bar|code-block|syntax|javascript|104767|我曾经像Bruce+P建议的那样，使用stat来做两个任务的方法。现在，我用creates作为一个任务来做这件事。我认为这要清楚得多。|104768|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I have found the creates option in the command module useful. How about this:

<pre><code>- name: Move foo to bar
 command: creates="path/to/bar" mv /path/to/foo /path/to/bar
</code></pre>

I used to do a 2 task approach using stat like Bruce P suggests. Now I do this as one task with creates. I think this is a lot clearer.

blocks|key|4611320|text|Bruce并没有试图统计目标以检查文件是否已经在那里移动；他在尝试mv之前确保要移动的文件确实存在。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4611321|如果你像Tom一样，只想在文件不存在的情况下移动文件，我认为我们仍然应该把Bruce的check整合到这个组合中：|4611322|-+name:+stat+foo
++stat:+path=/path/to/foo
++register:+foo_stat

-+name:+Move+foo+to+bar
++command:+creates="path/to/bar"+mv+/path/to/foo+/path/to/bar
++when:+foo_stat.stat.exists|code-block|syntax|javascript|4611323|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

Bruce wasn't attempting to stat the destination to check whether or not to move the file if it was already there; he was making sure the file to be moved actually existed before attempting the mv.

If your interest, like Tom's, is to only move if the file doesn't already exist, I think we should still integrate Bruce's check into the mix:

<pre><code>- name: stat foo
 stat: path=/path/to/foo
 register: foo_stat

- name: Move foo to bar
 command: creates="path/to/bar" mv /path/to/foo /path/to/bar
 when: foo_stat.stat.exists
</code></pre>

blocks|key|4611348|text|这就是我让它为我工作的方式：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|4611349|++Tasks:
++-+name:+checking+if+the+file+1+exists
+++++stat:++++++
++++++path:+/path/to/foo+abc.xts
+++++register:+stat_result

++-+name:+moving+file+1
++++command:+mv+/path/to/foo+abc.xts+/tmp
++++when:+stat_result.stat.exists+==+True|code-block|syntax|javascript|4611350|上面的攻略将检查文件abc.xts是否存在，然后再将文件移动到临时文件夹。|4611351|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

This is the way I got it working for me:

<pre><code> Tasks:
 - name: checking if the file 1 exists
 stat: 
 path: /path/to/foo abc.xts
 register: stat_result

 - name: moving file 1
 command: mv /path/to/foo abc.xts /tmp
 when: stat_result.stat.exists == True
</code></pre>

the playbook above, will check if file abc.xts exists before move the file to tmp folder.

blocks|key|104871|text|实现这一点的另一种方法是结合使用file和state:+hard。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|104872|这是我开始工作的一个例子：|104873|-+name:+Link+source+file+to+another+destination
++file:
++++src:+/path/to/source/file
++++path:+/target/path/of/file
++++state:+hard|code-block|syntax|javascript|104874|虽然只在本地主机(OSX)上测试过，但也应该可以在Linux上运行。对于Windows，我不能说。|104875|请注意，需要绝对路径。否则它不会让我创建链接。此外，您不能跨文件系统，因此使用任何已挂载的介质可能会失败。|104876|硬链接非常类似于移动，如果您随后删除源文件：|104877|-+name:+Remove+old+file
++file:
++++path:+/path/to/source/file
++++state:+absent|104878|另一个好处是，当你在一出戏的中间时，变化是持久的。因此，如果有人更改源文件，任何更改都会反映在目标文件中。|104879|您可以通过ls+-l验证指向文件的链接数量。硬链接的数量显示在模式旁边(例如，当文件有2个链接时，rwxr-xr-x+2)。|104880|entityMap^0|G|4|L|B|0|0|0|0|0|0|0|0|5|5|0^^$0|@$1|2|3|4|5|6|7|10|8|@$9|11|A|12|B|C]|$9|13|A|14|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|15|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|16|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|17|8|@]|D|@]|E|$]]|$1|O|3|P|5|6|7|18|8|@]|D|@]|E|$]]|$1|Q|3|R|5|6|7|19|8|@]|D|@]|E|$]]|$1|S|3|T|5|J|7|1A|8|@]|D|@]|E|$K|L]]|$1|U|3|V|5|6|7|1B|8|@]|D|@]|E|$]]|$1|W|3|X|5|6|7|1C|8|@$9|1D|A|1E|B|C]]|D|@]|E|$]]|$1|Y|3|-4|5|6|7|1F|8|@]|D|@]|E|$]]]|Z|$]]

Another way to achieve this is using <code>file</code> with <code>state: hard</code>.

This is an example I got to work: 

<pre><code>- name: Link source file to another destination
 file:
 src: /path/to/source/file
 path: /target/path/of/file
 state: hard
</code></pre>

Only tested on localhost (OSX) though, but should work on Linux as well. I can't tell for Windows.

Note that absolute paths are needed. Else it wouldn't let me create the link. Also you can't cross filesystems, so working with any mounted media might fail.

The hardlink is very similar to moving, if you remove the source file afterwards:

<pre><code>- name: Remove old file
 file:
 path: /path/to/source/file
 state: absent
</code></pre>

Another benefit is that changes are persisted when you're in the middle of a play. So if someone changes the source, any change is reflected in the target file.

You can verify the number of links to a file via <code>ls -l</code>. The number of hardlinks is shown next to the mode (e.g. rwxr-xr-x 2, when a file has 2 links).

blocks|key|104929|text|另一个对我来说效果很好的选择是使用+synchronize+module+。然后使用file模块删除原始目录。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|104930|下面是文档中的一个示例：|104931|-+synchronize:
++++src:+/first/absolute/path
++++dest:+/second/absolute/path
++++archive:+yes
++delegate_to:+"{{+inventory_hostname+}}"|code-block|syntax|javascript|104932|entityMap|0|LINK|mutability|MUTABLE|url|https://docs.ansible.com/ansible/latest/collections/ansible/posix/synchronize_module.html^0|H|K|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

Another Option that has worked well for me is using the <a href="https://docs.ansible.com/ansible/latest/collections/ansible/posix/synchronize_module.html" rel="nofollow noreferrer"> synchronize module </a>. Then remove the original directory using the file module.
Here is an example from the docs:
<pre><code>- synchronize:
 src: /first/absolute/path
 dest: /second/absolute/path
 archive: yes
 delegate_to: &quot;{{ inventory_hostname }}&quot;
</code></pre>

blocks|key|4611525|text|-+name:+Move+the+src+file+to+dest
++command:+mv+/path/to/src+/path/to/dest
++args:
++++removes:+/path/to/src
++++creates:+/path/to/dest|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|4611526|该命令仅在/path/to/src存在而/path/to/dest不存在的情况下运行mv命令，因此它在每个主机上运行一次，移动文件，然后不再运行。|unstyled|offset|length|style|CODE|4611527|当我需要移动数百台主机上的文件或目录时，我会使用这种方法，其中许多主机在任何给定时间都可能关机。它是幂等的，并且可以安全地留在剧本中。|4611528|entityMap^0|0|5|C|K|D|16|2|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$B|C]]|$1|D|3|E|5|F|7|P|8|@$G|Q|H|R|I|J]|$G|S|H|T|I|J]|$G|U|H|V|I|J]]|9|@]|A|$]]|$1|K|3|L|5|F|7|W|8|@]|9|@]|A|$]]|$1|M|3|-4|5|F|7|X|8|@]|9|@]|A|$]]]|N|$]]

<pre><code>- name: Move the src file to dest
 command: mv /path/to/src /path/to/dest
 args:
 removes: /path/to/src
 creates: /path/to/dest
</code></pre>
This runs the <code>mv</code> command only when <code>/path/to/src</code> exists and <code>/path/to/dest</code> does not, so it runs once per host, moves the file, then doesn't run again.
I use this method when I need to move a file or directory on several hundred hosts, many of which may be powered off at any given time. It's idempotent and safe to leave in a playbook.

blocks|key|105004|text|-+name:+Example
++hosts:+localhost
++become:+yes

++tasks:
++-+name:+checking+if+a+file+exists
++++stat:
++++++path:+"/projects/challenge/simplefile.txt"
++++register:+file_data
++
++-+name:+move+the+file+if+file+exists
++++copy:+
++++++src:+/projects/challenge/simplefile.txt
++++++dest:+/home/user/test
++++when:+file_data.stat.exists

++-+name:+report+a+missing+file
++++debug:+
++++++msg:+"the+file+or+directory+doesn't+exist"
++++when:+not+file_data.stat.exists|type|code-block|depth|inlineStyleRanges|entityRanges|data|syntax|javascript|105005|unstyled|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|G|8|@]|9|@]|A|$B|C]]|$1|D|3|-4|5|E|7|H|8|@]|9|@]|A|$]]]|F|$]]

<pre><code>- name: Example
 hosts: localhost
 become: yes

 tasks:
 - name: checking if a file exists
 stat:
 path: &quot;/projects/challenge/simplefile.txt&quot;
 register: file_data
 
 - name: move the file if file exists
 copy: 
 src: /projects/challenge/simplefile.txt
 dest: /home/user/test
 when: file_data.stat.exists

 - name: report a missing file
 debug: 
 msg: &quot;the file or directory doesn't exist&quot;
 when: not file_data.stat.exists
</code></pre>

How is it possible to move/rename a file/directory using an Ansible module on a remote system? I don't want to use the command/shell tasks and I don't want to copy the file from the local system to the remote system.

How to move/rename a file using an Ansible task on a remote system

如何使用Ansible模块在远程系统上移动/重命名文件/目录？我不想使用命令/shell任务，也不想将文件从本地系统复制到远程系统。

问如何在远程系统上使用Ansible任务移动/重命名文件
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在远程系统上使用Ansible任务移动/重命名文件EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问如何在远程系统上使用Ansible任务移动/重命名文件
EN