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

Unable to edit http repo credentials from argocd UI - openshift-gitops

XMLWordPrintable

    • GitOps Tangerine - Sprint 3269, GitOps Tangerine - Sprint 3270, GitOps Tangerine Sprint 12

      Description of Problem

      • Unable  to edit http repo credentials from argocd UI. The  repos hosted with http are not clickable from UI

      Additional Info

      • <Any additional info such as logs, must-gather outputs, etc.>

      Problem Reproduction

      • Add a repo hosted with http to argocd and try to click the repo in-order to modify the credentials

      Reproducibility

      • Always

      Prerequisites/Environment

      • openshift-gitoops 1.14

      Steps to Reproduce

      • Add a repo hosted with http to argocd and try to click the repo in-order to modify the credentials

      Expected Results

      • The repo should be clickable and able to modify the credentials via UI

      Actual Results

      • The repo is not clickable and so unable to modify the credentials

      Problem Analysis

      • <Completed by engineering team as part of the triage/refinement process>

      Root Cause

      • <What is the root cause of the problem? Or, why is it not a bug?>

      Workaround (If Possible)

      • Changing the credentials directly via secret yaml

      Fix Approaches

      • <If we decide to fix this bug, how will we do it?>

      Acceptance Criteria

      • ...

      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.

              rh-ee-atali Atif Ali
              rhn-support-gio Ginilekshmi A O
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: