From f1e41cbb366c7625631ecefe96e835bd647afece Mon Sep 17 00:00:00 2001 From: Martin Krizek Date: Wed, 11 Apr 2018 20:45:59 +0200 Subject: [PATCH] playbooks_intro.rst: remove duplicite playbook (#38521) --- .../rst/user_guide/playbooks_intro.rst | 33 ------------------- 1 file changed, 33 deletions(-) diff --git a/docs/docsite/rst/user_guide/playbooks_intro.rst b/docs/docsite/rst/user_guide/playbooks_intro.rst index 54363c3c06..bfd2488215 100644 --- a/docs/docsite/rst/user_guide/playbooks_intro.rst +++ b/docs/docsite/rst/user_guide/playbooks_intro.rst @@ -54,39 +54,6 @@ can run different plays at different times. For starters, here's a playbook that contains just one play:: - --- - - hosts: webservers - vars: - http_port: 80 - max_clients: 200 - remote_user: root - tasks: - - name: ensure apache is at the latest version - yum: - name: httpd - state: latest - - name: write the apache config file - template: - src: /srv/httpd.j2 - dest: /etc/httpd.conf - notify: - - restart apache - - name: ensure apache is running (and enable it at boot) - service: - name: httpd - state: started - enabled: yes - handlers: - - name: restart apache - service: - name: httpd - state: restarted - -When working with tasks that have really long parameters or modules that take -many parameters, you can break tasks items over multiple lines to improve the -structure. Below is another version of the above example but using -YAML dictionaries to supply the modules with their ``key=value`` arguments.:: - --- - hosts: webservers vars: