Uploaded image for project: 'Hybrid Cloud Console'
  1. Hybrid Cloud Console
  2. RHCLOUD-19905

[Playbook Dispatcher] Create Connector for Sources API

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • Unset
    • None
    • Platform Pipeline Sprint 43, Platform Pipeline Sprint 44, Platform Pipeline Sprint 45, Platform Pipeline Sprint 47, Platform Pipeline Sprint 48, Platform Pipeline Sprint 49, Platform Pipeline Sprint 50, Platform Pipeline Sprint 51

      In order to implement the High level Playbook Dispatcher API feature, the dispatcher must first have the capability to call the Sources API to gather importaint recipient information from a number of the endpoints.

      For the purpose of the High Level API we should communicate with the v3.1 version of the Sources API since it's the latest version and currently holds all endpoints needed for the dispatching of playbooks, specifically:

      1.  /sources/v3.1/sources/<satellite_instance_id>/rhc_connections
      2. /sources/v3.1/sources/v3.1/sources

      With these two endpoints we should be able grab all the information needed for the dispatching of playbooks for Direct Connected systems and Satellite RHC systems.

      IMPORTANT NOTE:  In the context of the sources API the satellite_instance_id and source_id refer to the same identifier

      REFERENCES: If you're looking for examples on how to implement this insights-remediations has a connector implemented for sources that would be a helpful resource:
      https://github.com/RedHatInsights/insights-remediations/blob/master/src/connectors/sources/impl.js

              alcohan-fifi Alec Cohan
              alcohan-fifi Alec Cohan
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: