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

Expose "extraargs" to be passed to repo server command line options

XMLWordPrintable

    • 8
    • False
    • None
    • False
    • Hide
      With this update, Users will be able to pass command arguments to the repo-server deployment using Argo CD CR.

      For example:
      ```
      apiVersion: argoproj.io/v1alpha1
      kind: ArgoCD
      metadata:
        name: example-argocd
      spec:
        repo:
          extraRepoCommandArgs:
            - --foo
            - bar
      ```
      Show
      With this update, Users will be able to pass command arguments to the repo-server deployment using Argo CD CR. For example: ``` apiVersion: argoproj.io/v1alpha1 kind: ArgoCD metadata:   name: example-argocd spec:   repo:     extraRepoCommandArgs:       - --foo       - bar ```
    • GITOPS Sprint 230

      Story (Required)

      As an administrator trying to provision OpenShift GitOps using GitOps Operator I want to pass command line arguments to Repo Server.

      To goal of this story to add the ability pass arbitrary command line arguments to Repo Server.

      Background (Required)

      <Describes the context or background related to this story>

      Argo CD fixed this security vulnerably . However, to apply the fix, users need to set --reposerver.max.combined.directory.manifests.size command line arguments to start the repo server. Currently, GitOps Operator does not support passing this options or "extraargs" option.

      Out of scope

      <Defines what is not included in this story>

      Approach (Required)

      <Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

      Support "extraargs" option which is already supported by argocd server command. 

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • Users can pass "extraargs" option to repo server in GitOps Operator
      • Add unit tests and end to end tests
      • Propagate fix to mid-stream and built and tested in CPaaS successfully

      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

            aveerama@redhat.com Abhishek Veeramalla
            wtam_at_redhat William Tam
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

              Created:
              Updated:
              Resolved: