Epic Goal

Deprecate and drop .spec.initialRepositories & spec.repositoryCredentials fields in the ArgoCD CRD and plan their removal according to the upstream timeline.

Github Issue: https://github.com/argoproj-labs/argocd-operator/issues/1535 

Why is this important?

Support for repo configs in argocd-cm is already deprecated in upstream and planned(argoproj/argo-cd#19768) to be removed in Argo CD v3.0. Operator supports this upstream feature via .spec.initialRepositories & spec.repositoryCredentials fields in ArgoCD CR.

• https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#repository-credentials-example
• https://argocd-operator.readthedocs.io/en/latest/reference/argocd/#initial-repositories

Other Considerations

Do we want to continue supporting these fields in the operator by using a different internal mechanism to create the required repos and repo credentials in Argo CD?

It was decided to preserve upstream behaviour so we should drop the support. 

Definition of Ready

• The epic has been broken down into stories.
• Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project.
• 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.
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.