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

Investigate why argo rollouts shell auto-completion works with kubectl but not oc

XMLWordPrintable

    • 5
    • False
    • None
    • False
    • SECFLOWOTL-93 - Promote Rollouts to GA
    • GITOPS Service EE Sprint 3254, GitOps Scarlet - Sprint 2261

      Story (Required)

      As a user of Argo Rollouts on OpenShift I would like shell auto completion for the rollouts kubectl plugin to work with the oc command.  It currently does work with kubectl

      Background (Required)

      Enabling shell auto completion for a kubectl plugin in general is described here: https://github.com/kubernetes/enhancements/tree/master/keps/sig-cli/2379-kubectl-plugins#shell-completion-support 

      This PR https://github.com/argoproj/argo-rollouts/pull/3377 describes specifically what to do to enable auto completion for the rollouts plugin.  This works for the kubectl command.

       

      However it does not work for the oc command. This story is to investigate why.

      Acceptance Criteria (Mandatory)

      We have an understanding of why this isn't working and what needs to be done to fix it.

      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-rnaaz Rizwana Naaz
              jpitman63 John Pitman
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: