Uploaded image for project: 'Okapi'
  1. Okapi
  2. OKAPI-269

group routingEntries under appropriate interfaces

    XMLWordPrintable

Details

    • New Feature
    • Status: Closed (View Workflow)
    • P3
    • Resolution: Done
    • None
    • 1.1.0

    Description

      When discussing Folio-377, we realized that our ModuleDescriptor is not quite right. The problem is that permissions (and later, permission sets) will need to belong to an interface the module supports, and also to the RoutingEntries that need them. Therefore RoutingEntries should be handled under the provided interfaces, not globally for the whole module.

      We can still use global RoutingEntries for filter-like things like mod-authtoken, logging, and timing - things that don't provide a decided interface.

      We also need to have a new section for the system interfaces the module provides. At the moment we have the tenant interface, and soon we will have one more, for catching when modules get enabled for tenants, in the first instance to make sure mod-permission can add the module's permissions (and sets) into its database. Later, we will have more stuff like that.

      TestRail: Results

        Attachments

          Issue Links

            blocks

            Task - A task that needs to be done. FOLIO-487 use ModuleDescriptors provided in the root directory of each module repo

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            New Feature - New feature requests OKAPI-267 Define permission sets in ModuleDescriptor

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            New Feature - New feature requests OKAPI-268 Permission loading interface in Okapi

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Task - A task that needs to be done. CIRC-1 Adapt circulation module to use new Okapi path filtering

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Task - A task that needs to be done. CIRCSTORE-3 Adapt loan storage module to use new Okapi path filtering

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Umbrella - FOLIO-377 Permission model design

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Task - A task that needs to be done. METADATA-52 Adapt inventory and inventory storage module descriptors to use Okapi Path Filtering

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Activity

              People

                heikki Heikki Levanto
                heikki Heikki Levanto
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  Time Tracking

                    Estimated:
                    Original Estimate - Not Specified
                    Not Specified
                    Remaining:
                    Remaining Estimate - 0 minutes
                    0m
                    Logged:
                    Time Spent - 3 days, 1 hour, 30 minutes
                    3d 1h 30m

                    TestRail: Runs

                      TestRail: Cases