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

Sources availability check

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Major Major
    • hms-0.5, hms-0.4
    • None
    • Provisioning
    • None
    • Sources integration
    • 0% To Do, 0% In Progress, 100% Done
    • False
    • dev-ready, doc-ready, po-ready, qe-ready, ux-ready

      Goal:

      • Report availability of the source to the sources app
      • Both manual (user triggered) and background regular runs need to be implemented

      Acceptance Criteria:

      • User is able to trigger availability check from sources
      • We can easily run availability check on schedule, where the schedule can be easily tweaked.
      • Configuration of throttling is available.
      • Endpoint that triggers availability check for single source
      • Architecture documentation is available

      Open questions:

      • How to implement the scheduled availability check?

      Test scenario:

      • Trigger the status availability in Sources API
        • api/sources/v3.1/sources/{sourceID}/check_availability
      • wait few seconds
      • Verify the status of Source through the sources API

      Ready-Ready notes

      • UX involvement not needed

      Resources:

              aabramov@redhat.com Adi Abramovich (Inactive)
              oezr@redhat.com Ondrej Ezr
              Mayuri Hadole Mayuri Hadole
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: