Merge lp:~sinzui/launchpad/merge-db-permissions into lp:launchpad
| Status: | Merged |
|---|---|
| Approved by: | j.c.sackett on 2012-11-01 |
| Approved revision: | no longer in the source branch. |
| Merged at revision: | 16231 |
| Proposed branch: | lp:~sinzui/launchpad/merge-db-permissions |
| Merge into: | lp:launchpad |
| Prerequisite: | lp:~abentley/launchpad/releasefinder-perms |
| Diff against target: |
139 lines (+27/-22) 2 files modified
database/schema/security.cfg (+5/-21) lib/lp/registry/tests/test_personset.py (+22/-1) |
| To merge this branch: | bzr merge lp:~sinzui/launchpad/merge-db-permissions |
| Related bugs: |
| Reviewer | Review Type | Date Requested | Status |
|---|---|---|---|
| j.c.sackett (community) | 2012-11-01 | Approve on 2012-11-01 | |
|
Review via email:
|
|||
Commit Message
Give all scripts SELECT on access* tables; person merge triggers can complete.
Description of the Change
Person merge failed because DB triggers require SELECT on accessartifact.
-------
RULES
Pre-
* Add SELECT on accessartifact to person-merge-job
* Oh, I discussed adding safe permissions to groups instead of users
with William and Francis. Giving SELECT to all the access* tables
will let every script read the data needed for permission checking
* give SELECT on the access* tables for the script user.
* Remove the duplicate grants
ADDENDUM
* I see Aaron just added SELECT to an access* table to fix the same
problem in the PRF. I will merge his branch into mine.
QA
* Visit https:/
and ~ailo.at into ~zequence
* https:/
* If the page loads and does not show the merge notice, then
merge failed.
LINT
database/
lib/lp/
LoC
This is a fix for feature work.
TEST
./bin/test -vvc -t "(script|
./bin/test --vvc -t TestPersonSetMerge lp.registry.
IMPLEMENTATION
I Added a test that reproduces the SQL error. I updated the DB permissions
to allow the test to pass. I removed the duplicate permissions...note that
I also deleted a duplicate declaration for accessartifact for one user.
database/
lib/lp/

Looks good, thanks.