script monitor needs a database user
Bug #134012 reported by
Stuart Bishop
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Fix Released
|
High
|
Stuart Bishop |
Bug Description
All scripts should connect as a unique database user.
To fix this involves:
* Editing database/
* Updating jubany's pg_ident.conf to allow connections as the new user for forster.
* Updating the monitoring script to connect as the new user
* Rolling out the code.
Related branches
lp:~stub/launchpad/distinct-db-users
- Gavin Panella (community): Approve (code)
- Raphaël Badin (community): Approve (code*)
-
Diff: 14 lines (+7/-0)1 file modifieddatabase/schema/security.cfg (+7/-0)
Changed in launchpad: | |
importance: | Undecided → Medium |
status: | New → Confirmed |
tags: |
added: qa-untestable removed: qa-needstesting |
Changed in launchpad: | |
status: | In Progress → Fix Released |
To post a comment you must log in.
Untargeting from 1.1.19 due to no owner. Maybe we can get james to do this for 1.1.10? Stu can you ask him about this please?