Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-9366

Ingest Tekton task to a postgres table

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • AI
    • None
    • 3
    • False
    • Hide

      None

      Show
      None
    • False
    • 3
    • Pipelines Sprint CrookShank 43

      Story (Required)

      As a developer trying to ingest all available Tekton tasks to DB I want to write a script that reads all metadata and source code from artifact hub and stores is in a POSTGRES separate table

      In order to match jenkins plugins to Tekton tasks I want to create 2 tables in a single DB that an agent can access both and find the equivalent based on the description/metadata.

      Background (Required)

      Plugin 2 Tasks match

      Out of scope

      write the agent's logic to search both tables

      Approach (Required)

      find a python lib that reads from web, access https://artifacthub.io/packages/search?repo=tekton-catalog-tasks cretae an object for each task in the db

      Dependencies

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

      Acceptance Criteria (Mandatory)

      <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>

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      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 etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              rh-ee-ngelman Naomi Gelman
              rh-ee-ngelman Naomi Gelman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: