Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-10329

Make variables in the AI software template resources consistent

    • Icon: Story Story
    • Resolution: Done
    • Icon: Minor Minor
    • None
    • None
    • None
    • DEVAI Sprint 3276

      Story (Required)

      As a developer working on the AI software templates, the template variables used in the GitOps template (and pipeline if affected too) should be consistent and use the format that RHDH expects (${{ values.xyz }})

      Background (Required)

      Currently, the GitOps template defined in https://github.com/redhat-ai-dev/ai-lab-app use a non-standard format of variable templating ({{value.xyz{}}}) that is not directly compatible with Backstage templates. As a result, the script that pulls in the gitops skeleton into the AI software template, needs to modify the template variables in order to be compatible with RHDH (see https://github.com/redhat-ai-dev/ai-lab-template/blob/main/scripts/import-gitops-template#L33-L50).

      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 DEVHAS team only)
      R&D label required (Filled by DEVHAS 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

              rh-ee-lyoon Lucas Yoon
              johnmcollier John Collier
              RHIDP - AI
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: