Uploaded image for project: 'stripes-core'
  1. stripes-core
  2. STCOR-114

Update collection of Okapi information

    XMLWordPrintable

Details

    Description

      Currently, it appears that Stripes uses the /_/proxy/modules Okapi endpoint to gather information about modules, then iterates over the full list to gather information about interfaces. It does this before presenting the login prompt. This creates a large number of requests in the case when there are a large number of modules registered with Okapi (as after a pull from a central module descriptor registry).

      Perhaps it would be better to use the /_/proxy/tenants/<tenantId>/modules endpoint to build the list, so that you see only the interfaces of the modules configured for the Stripes tenant.

      It might also be good to collect this information at some other point in the Stripes initialization process, so that the prompt isn't delayed.

      Finally, it might be interesting to look at creating other Okapi endpoints to provide the information Stripes needs – for example, something like /_/proxy/tenants/<tenantId>/interfaces to show all the interfaces available to the tenant.

      TestRail: Results

        Attachments

          Issue Links

            Activity

              People

                zburke Zak_Burke
                wayne Wayne Schneider
                Votes:
                0 Vote for this issue
                Watchers:
                7 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 - 1 hour, 30 minutes
                    1h 30m

                    TestRail: Runs

                      TestRail: Cases