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

Configure appInformer in Principal and Agent startup

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • ArgoCD
    • GitOps Tangerine - Sprint 3263

      Story (Required)

      When the principal starts up, the principal should be able to configure ProjectInformer and start watch on all the AppProjects configured in control plane.

      Similarly, when the agent starts up, the agent should be able to configure ProjectInformer and start watch on all the AppProjects configured on the agent.

      Background (Required)

      When the principal starts up, it lists all currently existing AppProjects on the control plane as part of the informer setup and configures the watch. As no agents can be connected until the informer is ready, no further action is required at this point.

       

      Similarly, when the agent starts up, the agent should be able to configure ProjectInformer and start watch on all the AppProjects configured on the agent.

      Out of scope

      Approach (Required)

      The projectInformer is already present on the argo-agent in https://github.com/ishitasequeira/argocd-agent/tree/7b36a131837da892d41c0c0ccfff4d99b228df92/internal/informer/appproject.

      • We need to add projectInformer to the Principal server similar to how we configure appInformer here
      • We need to add projectInformer to the Agent server similar to how we configure appInformer here

       

      Dependencies

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

      Acceptance Criteria (Mandatory)

      • The principal and agent starts with projectInformer configured.
      • Add required unit tests for the code change.
      • CI checks succeed.

       

      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

              isequeir@redhat.com Ishita Sequeira
              isequeir@redhat.com Ishita Sequeira
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: