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

Argo CD: Introduce a command to the CLI that gets live manifests

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • ArgoCD
    • None
    • Argo CD: Introduce a command to the CLI that gets live manifests
    • False
    • Hide

      None

      Show
      None
    • False
    • In Progress
    • 0% To Do, 0% In Progress, 100% Done

      Epic Goal

      • Implement a command in the Argo CD CLI that gives the user the ability to get the live manifest of a resource within in application. 

      Related issue on GitHub:

      https://github.com/argoproj/argo-cd/issues/23196

      Why is this important?

      • This feature is useful to user's for debugging, monitoring, and other operational tasks. With this command you will not need to give direct access to kubectl. 

      Scenarios

      1. ...

      Other Considerations

      • <Call out anything explicitly as Out of Scope?>
      • <Call out internal and external dependencies?>
      • <Are there any known previous works?>
      • <Any unanswered questions?>

      Definition of Ready

      • The epic has been broken down into stories.
      • Stories have been scoped.
      • The epic has been stack ranked.

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Integration tests have been completed.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written.
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
      • Review:
        • Code has been peer-reviewed and meets coding standards.
        • All acceptance criteria defined in the user story have been met.
        • Tested by reviewer on OpenShift.
      • Deployment:
        • The feature has been deployed on OpenShift cluster for testing.
      • Acceptance:
        • Product Manager or stakeholder has reviewed and accepted the work.

              rh-ee-ccoco Christopher Coco (Inactive)
              rh-ee-ccoco Christopher Coco (Inactive)
              Tangerine
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: