Story (Required)

To use RHDH Lightspeed with Lightspeed-core as backend upstream, it is required that the information and configuration set in RHDH config can be pass in to Lightspeed-core container.

Background (Required)

This was done in road-core by passing in the RHDH configmap as a env to road-core container.

we should do similar thing for lightspeed-core, the configuration will then take place & override lightspeed-core

Acceptance Criteria

• RHDH config file can be passed to lightspeed-core container and lightspeed-core handles the data and loads it into the necessary objects.

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Required)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

documentation updates (design docs, release notes etc)
demo needed
SOP required
education module update (Filled by RHDHPAI team only)
R&D label required (Filled by RHDHPAI team only)

Done Checklist

Code is completed, reviewed, documented and checked in
Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
Continuous Delivery pipeline(s) is able to proceed with new code included
Customer facing documentation, API docs, design docs etc. are produced/updated, reviewed and published
Acceptance criteria are met
If the Grafana dashboard is updated, ensure the corresponding SOP is updated as well