1. Ansible provides a self-documenting way of deploying both the software and database content—coupled with a tool such as AWX, it ensures you have an audit trail of who made what changes and when.
2. Create the configuration file as a template and deploy it using the template across all servers. Where configurations are split across multiple files, either ensure that all files are managed by Ansible or remove the include statement from the files to ensure parameters cannot be accidentally overridden.
3. Ansible performs all its operations on the database machine using SSH—hence, there is no need to open your database server to the network to manage it.
4. You would use the shell module when the native module you need cannot perform the operation you require. For example, older versions of Ansible could do most things on PostgreSQL, but couldn...