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

Enable users to run CLI commands related to Argo Applications in any namespace

XMLWordPrintable

    • Enable users to run CLI commands related to Argo Applications in any namespace
    • False
    • None
    • False
    • To Do
    • SECFLOWOTL-97 - Promote Applications in Any Namespace to GA
    • 0% To Do, 0% In Progress, 100% Done
    • Hide
      With this update, the ArgoCD CLI has been enhanced by enabling the --app-namespace flag for various application-related commands. This flag allows users to specify the namespace for operations such as waiting, rolling back, patching, editing, diffing, viewing history, syncing, and deleting applications.

      Commands Updated:

      argocd app wait
      argocd app rollback
      argocd app patch
      argocd app edit
      argocd app diff
      argocd app history
      argocd app sync
      argocd app delete
      argocd app get
      Show
      With this update, the ArgoCD CLI has been enhanced by enabling the --app-namespace flag for various application-related commands. This flag allows users to specify the namespace for operations such as waiting, rolling back, patching, editing, diffing, viewing history, syncing, and deleting applications. Commands Updated: argocd app wait argocd app rollback argocd app patch argocd app edit argocd app diff argocd app history argocd app sync argocd app delete argocd app get
    • Feature
    • In Progress

      Epic Goal

      • Stablize the "Apps in Any Namespace" feature and bring it to GA

       

      Upstream ticket: https://github.com/argoproj/argo-cd/issues/16189

      Why is this important?

      • ...

      Scenarios

      1. ...

      Acceptance Criteria (Mandatory)

      • CI - MUST be running successfully with tests automated
      • Release Technical Enablement - Provide necessary release enablement details and documents.
      • ...

      Dependencies (internal and external)

      1. ...

      Previous Work (Optional):

      1. ...

      Open questions::

      1. ...
      •  

      Done Checklist

      • Acceptance criteria are met
      • Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
      • User Journey automation is delivered
      • Support and SRE teams are provided with enough skills to support the feature in production environment

              rh-ee-mmeetei Mangaal Meetei
              rh-ee-anjoseph Anand Francis Joseph
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: