{"push_id":2336871079,"size":1,"distinct_size":1,"ref":"refs/heads/jmhooper-readonly-db-users","head":"f8ced69ed7d685c9a887ececc93b9b6e2d6448f9","before":"9f7ffc7073f96f7afec854ab519c3d5bbcd9b493","commits":[{"sha":"f8ced69ed7d685c9a887ececc93b9b6e2d6448f9","author":{"name":"Jonathan Hooper","email":"5ace0b113155c1000e733920652c7966c1d1fe5f@gsa.gov"},"message":"Use readonly production database config in console\n\n**Why**: So that console users in deployed environments will not be able\nto modify records without explicitly enabling write access. Enabling\nwrite access is done by setting ALLOW_CONSOLE_DB_WRITE_ACCESS=true.\n\n**How**: This commit adds a class called ProductionDatabaseConfiguration\nwhich is loaded in database.yml and used to determine the value of\nconfigs such as the username, password, and pool size. When the rails\nconsole is defined, it uses 2 new configs for user name and password\nthat should correspond to a read only user.","distinct":true,"url":"https://api.github.com/repos/18F/identity-idp/commits/f8ced69ed7d685c9a887ececc93b9b6e2d6448f9"}]}
{"actor":{"display_login":"jmhooper"}}