removed deprecated user in favor of remote_user

jboss-standalone/site.yml

@@ -2,7 +2,7 @@
 # This playbook deploys a simple standalone JBoss server. 
 
 - hosts: jboss-servers 
-  user: root
+  remote_user: root
 
   roles:
     - jboss-standalone

lamp_haproxy/rolling_update.yml

@@ -12,7 +12,7 @@
   tasks: []
 
 - hosts: webservers
-  user: root
+  remote_user: root
   serial: 1
 
   # These are the tasks to run before applying updates:

lamp_haproxy/site.yml

@@ -3,34 +3,34 @@
 
 # Apply common configuration to all hosts
 - hosts: all
-  user: root
+  remote_user: root
   roles:
   - common
 
 # Configure and deploy database servers.
 - hosts: dbservers
-  user: root
+  remote_user: root
   roles:
   - db
 
 # Configure and deploy the web servers. Note that we include two roles here, 
 # the 'base-apache' role which simply sets up Apache, and 'web' which includes
 # our example web application.
 - hosts: webservers
-  user: root
+  remote_user: root
   roles:
   - base-apache
   - web
 
 # Configure and deploy the load balancer(s).
 - hosts: lbservers
-  user: root
+  remote_user: root
   roles:
   - haproxy
 
 # Configure and deploy the Nagios monitoring node(s).
 - hosts: monitoring
-  user: root
+  remote_user: root
   roles:
   - base-apache
   - nagios

language_features/ansible_pull.yml

@@ -16,7 +16,7 @@
 ---
 
 - hosts: pull_mode_hosts
-  user: root
+  remote_user: root
 
   vars:
 

language_features/conditionals_part1.yml

@@ -14,7 +14,7 @@
 # as root
 
 - hosts: all
-  user: root
+  remote_user: root
 
 # we have a common list of variables stored in /vars/external_vars.yml
 # that we will always import

language_features/conditionals_part2.yml

@@ -3,7 +3,7 @@
 # certain tasks on machines/platforms/etc where they do not apply.  
 
 - hosts: all
-  user: root
+  remote_user: root
 
   vars:
      favcolor: "red"

language_features/environment.yml

@@ -8,7 +8,7 @@
 
 
 - hosts: all
-  user: root
+  remote_user: root
 
   # here we make a variable named "env" that is a dictionary
   vars:

language_features/eucalyptus-ec2.yml

@@ -14,7 +14,7 @@
 - name: Stage instance(s)
   hosts: local
   connection: local
-  user: root
+  remote_user: root
   gather_facts: false
 
   vars:
@@ -53,7 +53,7 @@
 # This play targets the new host group
 - name: Configure instance
   hosts: deploy
-  user: root
+  remote_user: root
 
   # Do some stuff on each instance ....
 

language_features/file_secontext.yml

@@ -1,7 +1,7 @@
 ---
 # This is a demo of how to manage the selinux context using the file module
 - hosts: test
-  user: root
+  remote_user: root
   tasks:
     - name: Change setype of /etc/exports to non-default value
       file: path=/etc/exports setype=etc_t

language_features/group_commands.yml

@@ -2,7 +2,7 @@
 # This is a demo of how the group command works.
 
 - hosts: all
-  user: root
+  remote_user: root
   sudo: yes
 
   tasks:

language_features/intermediate_example.yml

@@ -67,7 +67,7 @@
 # if you want.  sudo support is coming too.
 
 - hosts: webservers
-  user: mdehaan
+  remote_user: mdehaan
 
   # vars must be specified again for the next play in the playbook
   # but can be reused by including from vars_files if you want

language_features/intro_example.yml

@@ -9,10 +9,10 @@
 
 - name: example play
   hosts: all
-  user: root
+  remote_user: root
 
 # could have also have done:
-#  user: mdehaan
+#  remote_user: mdehaan
 #  sudo: yes
 
   # make these variables available inside of templates

language_features/loop_with_items.yml

@@ -4,7 +4,7 @@
 # multiple users
 
 - hosts: all
-  user: root
+  remote_user: root
 
   tasks:
 

language_features/mysql.yml

@@ -4,7 +4,7 @@
 
 ---
 - hosts: all
-  user: root
+  remote_user: root
 
   tasks:
 

language_features/nested_playbooks.yml

@@ -10,7 +10,7 @@
 
 - name: this is a play at the top level of a file
   hosts: all
-  user: root
+  remote_user: root
   tasks:
   - name: say hi
     tags: foo

language_features/prompts.yml

@@ -4,7 +4,7 @@
 # of a playbook run, for example, as part of a release script.
 
 - hosts: all
-  user: root
+  remote_user: root
 
 # regular variables are a dictionary of keys and values
 

language_features/register_logic.yml

@@ -4,7 +4,7 @@
 # easy to do, and here we'll show you how.
 
 - name: test playbook
-  user: root
+  remote_user: root
   hosts: all
 
   tasks:

language_features/tags.yml

@@ -13,7 +13,7 @@
 
 - name: example play one
   hosts: all
-  user: root
+  remote_user: root
 
   # any tags applied to the play are shorthand to applying
   # the tag to all tasks in it.  Here, each task is given
@@ -33,7 +33,7 @@
 
 - name: example play two
   hosts: all
-  user: root
+  remote_user: root
   tasks:
   - name: hi
     tags:

language_features/user_commands.yml

@@ -3,7 +3,7 @@
 # in vars sections.  You could also use vars_files if you like (see other examples)
 
 - hosts: all
-  user: root
+  remote_user: root
   vars:
     # created with:
     # python -c 'import crypt; print crypt.crypt("This is my Password", "$1$SomeSalt$")'

mongodb/playbooks/testsharding.yml

@@ -2,7 +2,7 @@
 # The playbook creates a new database test and populates data in the database to test the sharding.
 
 - hosts: $servername
-  user: root
+  remote_user: root
   tasks:
    - name: Create a new database and user
      mongodb_user: login_user=admin login_password=${mongo_admin_pass} login_port=${mongos_port} database=test user=admin password=${mongo_admin_pass} state=present

tomcat-standalone/site.yml

@@ -2,7 +2,7 @@
 # This playbook deploys a simple standalone Tomcat 7 server. 
 
 - hosts: tomcat-servers 
-  user: root
+  remote_user: root
 
   roles:
     - selinux

wordpress-nginx/site.yml

@@ -1,7 +1,7 @@
 ---
 - name: Install WordPress, MySQL, Nginx, and PHP-FPM
   hosts: wordpress-server
-  user: root
+  remote_user: root
   # remote_user: user
   # sudo: yes