You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the Ansible local provisioner to set up a Vagrant test machine. The installed Postgresql database server should trust any incoming connection, so my playbook.yml looks something like this:
---
- name: Set up the Vagrant development server
hosts: all
become: yes
vars:
postgresql_hba_entries:
- { type: local, database: all, user: all, auth_method: trust }
- { type: host, database: all, user: all, address: '127.0.0.1/32', auth_method: trust }
- { type: host, database: all, user: all, address: '::1/128', auth_method: trust }
roles:
- role: geerlingguy.postgresql
Installation works, but the postgresql role is skipping the step to configure the pg_hba.conf file, meaning I have to manually make my changes in pg_hba.conf to connect to the database server.
Is there a mistake in my playbook.yml or might this be a bug because my configuration is "too similar" to the defaults?
The text was updated successfully, but these errors were encountered:
This issue has been marked 'stale' due to lack of recent activity. If there is no further activity, the issue will be closed in another 30 days. Thank you for your contribution!
Please read this blog post to see the reasons why I mark issues as stale.
I am using the Ansible local provisioner to set up a Vagrant test machine. The installed Postgresql database server should trust any incoming connection, so my playbook.yml looks something like this:
Installation works, but the postgresql role is skipping the step to configure the pg_hba.conf file, meaning I have to manually make my changes in pg_hba.conf to connect to the database server.
Is there a mistake in my playbook.yml or might this be a bug because my configuration is "too similar" to the defaults?
The text was updated successfully, but these errors were encountered: