diff options
| author | Abhijeet Kasurde <akasurde@redhat.com> | 2017-06-12 12:25:19 +0530 |
|---|---|---|
| committer | John R Barker <john@johnrbarker.com> | 2017-06-12 07:55:19 +0100 |
| commit | b89cb956092e6f28d16010dc887ee2dc46e7855b (patch) | |
| tree | 0162132b7c833888bc16a32c6d5e251245aedd03 /docs/docsite/rst/intro_windows.rst | |
| parent | 460d932aa8e8fbdc0c72057e2e43f6e98d1d590c (diff) | |
| download | ansible-b89cb956092e6f28d16010dc887ee2dc46e7855b.tar.gz | |
Fix spelling mistakes (comments only) (#25564)
Original Author : klemens <ka7@github.com>
Taking over previous PR as per
https://github.com/ansible/ansible/pull/23644#issuecomment-307334525
Signed-off-by: Abhijeet Kasurde <akasurde@redhat.com>
Diffstat (limited to 'docs/docsite/rst/intro_windows.rst')
| -rw-r--r-- | docs/docsite/rst/intro_windows.rst | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/docsite/rst/intro_windows.rst b/docs/docsite/rst/intro_windows.rst index abd173d55e..438f548c39 100644 --- a/docs/docsite/rst/intro_windows.rst +++ b/docs/docsite/rst/intro_windows.rst @@ -55,7 +55,7 @@ At the prompt you can quickly start using the Ansible devel branch by running th git clone https://github.com/ansible/ansible.git source ansible/hacking/env-setup -After you've successfully run these commands, you can start to create your inventory, write example playbooks and start targetting systems using the plethora of available Windows modules. +After you've successfully run these commands, you can start to create your inventory, write example playbooks and start targeting systems using the plethora of available Windows modules. .. Note:: Ansible is also reported to work on Cygwin, but this is more cumbersome and doesn't scale as well as WSL. @@ -469,7 +469,7 @@ You may wind up with a more readable playbook by using the PowerShell equivalent - name: Move file on remote Windows Server from one location to another win_command: Powershell.exe "Move-Item C:\teststuff\myfile.conf C:\builds\smtp.conf" -Bear in mind that using ``win_command`` or ``win_shell`` will always report ``changed``, and it is your responsiblity to ensure PowerShell will need to handle idempotency as appropriate (the move examples above are inherently not idempotent), so where possible use (or write) a module. +Bear in mind that using ``win_command`` or ``win_shell`` will always report ``changed``, and it is your responsibility to ensure PowerShell will need to handle idempotency as appropriate (the move examples above are inherently not idempotent), so where possible use (or write) a module. Here's an example of how to use the ``win_stat`` module to test for file existence. Note that the data returned by the ``win_stat`` module is slightly different than what is provided by the Linux equivalent:: |