From 128be9ea27277f40694847748ace56c0c01e6ae2 Mon Sep 17 00:00:00 2001 From: Michael DeHaan Date: Wed, 18 Jun 2014 16:42:51 -0500 Subject: [PATCH] File rename. --- docsite/rst/intro_windows.rst | 4 ++-- examples/scripts/{UpgradeToPS3.ps1 => upgrade_to_ps3.ps1} | 0 2 files changed, 2 insertions(+), 2 deletions(-) rename examples/scripts/{UpgradeToPS3.ps1 => upgrade_to_ps3.ps1} (100%) diff --git a/docsite/rst/intro_windows.rst b/docsite/rst/intro_windows.rst index 51e2d4db24e..26cdffb64bf 100644 --- a/docsite/rst/intro_windows.rst +++ b/docsite/rst/intro_windows.rst @@ -151,13 +151,13 @@ Additionally, Powershell 3.0 or higher is needed for most modules. You can actu ansible example playbook to upgrade your windows systems from Powershell 2.0 to 3.0 in order to take advantage of the *other* ansible modules. -Looking at an ansible checkout, copy the examples/scripts/upgrade_ps2_to_3.ps1 script from the repo into +Looking at an ansible checkout, copy the examples/scripts/upgrade_to_ps3.ps1 script from the repo into your local directory, and run a playbook that looks like the following:: - hosts: windows gather_facts: no tasks: - - script: upgrade_ps2_to_3.ps1 + - script: upgrade_to_ps3.ps1 The hosts in the above group will then be running a new enough version of Powershell to be managed by the full compliment of Ansible modules. diff --git a/examples/scripts/UpgradeToPS3.ps1 b/examples/scripts/upgrade_to_ps3.ps1 similarity index 100% rename from examples/scripts/UpgradeToPS3.ps1 rename to examples/scripts/upgrade_to_ps3.ps1