Done
Details
Assignee
Oleksii KuzminovOleksii KuzminovReporter
Craig McNallyCraig McNallyPriority
P1Story Points
2Sprint
NoneDevelopment Team
EurekaFix versions
TestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Oleksii Kuzminov
Oleksii KuzminovReporter
Craig McNally
Craig McNallyPriority
Story Points
2
Sprint
None
Development Team
Eureka
Fix versions
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 19, 2024 at 10:52 PM
Updated April 25, 2024 at 9:11 AM
Resolved February 26, 2024 at 12:38 PM
Pavel provided a list of “duplicate” capabilities. We need to update our mapping file to cover these.
This issue can be reproduced locally in debug mode:
Skip modules installation for app-platform-complete (FolioModuleInstaller Stage)
Install app-platform-minimal + app-platform-complete (use latest application descriptors Poppy SP1)
Scope
Duplicated capabilities - requires changes in community codebase (out of scope)
Capabilities were not created—reasons: order of module installations, and custom mapping do not cover these cases.
order installations - significant work and requires a lot of investigations(out of scope for now)
Update the custom mapping file in mod-roles-keycloak and include values for unknown permissions(“
Capability action is not resolved
“ in log)Fix permissions where we have permName in the handlers section but particular permission was not defined in the permissionSets section of Module Descriptor. (
Permission value is not found: permissionName
in logs)Create issues for the community
Override module descriptors and put them into the https://github.com/folio-org/application-descriptors/tree/master/Poppy/mds
load MD from https://folio-registry.dev.folio.org/_/proxy/modules/
Ask DevOps to load an updated MD to the Eureka MDR
update link in application descriptors