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

Argo CD Agent: Application .spec.destination field can be used to map Applications to clusters

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • 1.20.0
    • None
    • Argo CD Agent
    • GitOps Scarlet Sprint 27

      Story (Required)

      See parent feature and corresponding GitHub issue https://github.com/argoproj-labs/argocd-agent/issues/593 for detailed description of the requirements

      Acceptance Criteria (Mandatory)

      • Note: if there is any refactoring to the existing code that might be beneficial BEFORE this feature is implemented, it might be a good idea to do this first (like, as an initial PR).
      • Once implemented, the existing namespace->cluster behaviour will remain in effect, but the new behaviour can optionally be enabled command line parameter/env var/etc.
      • The GitHub issue and parent feature currently best describe the expected behaviour, but the devil is in the details here : D.
        • The owner of the story may discover additional design problems that need to be discussed+solved during implementation.
      • Unit/E2E tests for new behaviour
      • We may wish to initially mark this new behaviour as experimental in the code/documentation.
      • This feature might be large, so we may want to optionally split this into multiple separate PRs
        • It is up to the story owner if they want to do this, e.g. if splitting it into multiple PRs is helpful

      Definition of Done

      • Code Complete:
        • All code has been written, reviewed, and approved.
      • Tested:
        • Unit tests have been written and passed.
        • Ensure code coverage is not reduced with the changes.
        • Integration tests have been automated.
        • System tests have been conducted, and all critical bugs have been fixed.
        • Tested and merged on OpenShift either upstream or downstream on a local build.
      • Documentation:
        • User documentation or release notes have been written (if applicable).
      • Build:
        • Code has been successfully built and integrated into the main repository / project.
        • Midstream changes (if applicable) are done, reviewed, approved and merged.
      • 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.

              cbanavik Chetan Banavikalmutt
              jgwest Jonathan West
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: