Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4672

incorporate`omc` tool for must-gather

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • 1.13.0
    • 1.13.0
    • None
    • 5
    • False
    • None
    • False
    • GitOps Crimson - Sprint 3257

      Story (Required)

      As a user of the gitops must-gather, I want to be able to use the `omc` tool to interact with the custom gitops must-gather. 

      Background (Required)

      We received a PR from a community member (https://github.com/redhat-developer/gitops-must-gather/pull/21https://github.com/redhat-developer/gitops-must-gather/pull/21) that incorporates the a tool that the community member themselves developed  called the `omc` tool, which allows users to interact with a collected must-gather the same way someone can use the `oc` tool with a live cluster. 

      We had a cabal meeting where Gabriel (the contributor) demoed the feature and everyone agreed that it's a change we would like to incorporate. 

      PR just needs to be tested thoroughly, merged, and then added to upstream sources and shipped with v1.13.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      • test PR and merge
      • update instructions in README for how to use the gitops must-gather based on the changes
      • add changes to upstream sources for 1.13

      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

            rescott1 Regina Scott (Inactive)
            rescott1 Regina Scott (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: