Currently, if we want to enable logging on any of the database servers in order to diagnose a problem (query logging, connection logging, etc.) we have to completely disable puppet for that server. This has become awkward and quite inconvenient, especially in weeks like the last one in which we spent 4 days trying to track down connection issues in Staging. I know it's possible for Puppet to just control specific lines of a conf file. Please find a way to do this which excludes the following: pgbouncer-processor.ini & pgbouncer-web.ini log_connections log_disconnections postgresql.conf log_* Thanks!
Brian, on IRC, said that the best way to do this is parameterized classes. Please work with Brian when you get back from PTO to set this up. Thanks!
Actually, there's a simpler way to do this. As we did for some other clients, we can move both PostgreSQL's logging parameters, and the two server IP addresses each to separate files. Then those files don't have to be under Puppet.
This is managed via puppet instead of hard-coded now, closing.