66fb7fd9de
At the moment Ansible prefers yes/no for module booleans, however booleans in playbooks are still using True/False, rather than yes/no. This changes modifies boolean uses in playbooks (and man pages) to favor yes/no rather than True/False. This change includes: - Adaptation of documentation and examples to favor yes/no - Modification to manpage output to favor yes/no (the docsite output already favors yes/no)
41 lines
No EOL
1 KiB
YAML
41 lines
No EOL
1 KiB
YAML
##
|
|
# Example Ansible playbook that uses the PostgreSQL module.
|
|
#
|
|
# This installs PostgreSQL on an Ubuntu system, creates a database called
|
|
# "myapp" and a user called "django" with password "mysupersecretpassword"
|
|
# with access to the "myapp" database.
|
|
#
|
|
---
|
|
- hosts: webservers
|
|
sudo: yes
|
|
gather_facts: no
|
|
|
|
tasks:
|
|
- name: ensure apt cache is up to date
|
|
action: apt update_cache=yes
|
|
- name: ensure packages are installed
|
|
action: apt pkg=$item
|
|
with_items:
|
|
- postgresql
|
|
- libpq-dev
|
|
- python-psycopg2
|
|
|
|
- hosts: webservers
|
|
sudo: yes
|
|
sudo_user: postgres
|
|
gather_facts: no
|
|
|
|
vars:
|
|
dbname: myapp
|
|
dbuser: django
|
|
dbpassword: mysupersecreetpassword
|
|
|
|
tasks:
|
|
- name: ensure database is created
|
|
action: postgresql_db db=$dbname
|
|
|
|
- name: ensure user has access to database
|
|
action: postgresql_user db=$dbname user=$dbuser password=$dbpassword priv=ALL
|
|
|
|
- name: ensure user does not have unnecessary privilege
|
|
action: postgresql_user user=$dbuser role_attr_flags=NOSUPERUSER,NOCREATEDB |