Implement static permission migration
Description
Environment
None
Potential Workaround
None
blocks
has to be finished together with
is blocked by
relates to
Checklist
hideTestRail: Results
Activity
Show:
Craig McNally November 24, 2020 at 3:22 PM
Blocked pending the outcome of spikes and
Done
Details
Details
Assignee
Craig McNallyReporter
Craig McNallyPriority
P2Story Points
5
Sprint
None
Development Team
Core: Platform
Fix versions
Release
R1 2021
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created November 10, 2020 at 6:21 PM
Updated May 4, 2022 at 2:56 PM
Resolved January 15, 2021 at 10:37 PM
TestRail: Cases
TestRail: Runs
Overview
OKAPI-839 investigated approaches to migrating static permissions during module upgrade. The outcome was a PoC and wiki page describing the preferred approach. This story follows that and formalizes/completes the implementation started in the PoC.
wiki page: https://folio-org.atlassian.net/wiki/display/DD/Migration+of+Static+Permissions+Upon+Upgrade
PoC: https://github.com/folio-org/okapi/pull/1038
NOTE: this work spans both OKAPI and mod-permissions. This story covers the OKAPI portion only.
Acceptance Criteria
No breaking changes - must support the existing version of the _tenantPermissions interface.
When the new version of _tenantPermissions is available, it should be used to handle static permission migration
Module downgrades must also be handled appropriately.