Uploaded image for project: 'Insights Experiences'
  1. Insights Experiences
  2. HMS-1711

IdP registry service - support path prefixes (WIP)

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Undefined Undefined
    • hms-0.7
    • None
    • Identity Management
    • None

      Goal: 

      • As a developer I want the backend service support /beta and /preview prefixes into the path.

      Acceptance Criteria:

      • Skippers works as expected when the path includes /beta or /preview for the different middlewares.
      • Router wire paths for /beta /preview and no prefix.
      • Metrics count the requests for /prefix and /beta paths.

      TODO1: About metrics, should be considered as different counters? or count the same /prefix than /beta than no prefix? I mean GET /beta/api/hmsidm/v1/domains will increase the same counter as GET /api/hmsidm/v1/domains ? Something to consider.

      TODO2: Related to TODO1, could the same deployment attend requests for no prefix, /beta and /preview prefixes? If no, the metrics are not mixed, else consider to label the metric, and store for the metric a normalized path (with no prefixes).

              Unassigned Unassigned
              avisiedo@redhat.com Alejandro Visiedo
              None
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: