ADMIN_PROXIMITY_ADJUSTMENT missing from seed data

Bug #1488511 reported by Galen Charlton
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Evergreen
New
Low
Josh Stompro

Bug Description

The ADMIN_PROXIMITY_ADJUSTMENT permission, which was defined in 2.4 as part of the calculated proximity adjustments feature, was not added to the seed data for new databases and was not added by an upgrade script. This means that anybody wishing to set OU proximity adjustments would need to add the permission manually (or have Evergreen superuser permissions).

Note that when this bug is fixed, the schema upgrade script should take into account the possibility that the permission had been manually added.

Evergreen master

Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

user/stompro/lp1488511_ADMIN_PROXIMITY_ADJUSTMENT

http://git.evergreen-ils.org/?p=working/Evergreen.git;a=shortlog;h=refs/heads/user/stompro/lp1488511_ADMIN_PROXIMITY_ADJUSTMENT

I took a stab at this, let me know if the update looks right, for checking to make sure the permission wasn't already added manually.
Josh

tags: added: pullrequest
Revision history for this message
Josh Stompro (u-launchpad-stompro-org) wrote :

I just did a forced update of the branch, to match how Blake added a permission entry for https://bugs.launchpad.net/evergreen/+bug/1456301

Added a PGTAP test, I don't really understand why the test is helpful. It seems to test if the permission can be added, not if it was already added. So it will detect if it is no longer possible to add a permission entry?

Josh

tags: added: permissions
Changed in evergreen:
assignee: nobody → Josh Stompro (u-launchpad-stompro-org)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.