Epic Goal

As a user of argocd-agent, I should be able to create and manage repository credentials from the control plane. The argocd-agent should sync these repositories to the appropriate workload clusters.

Why is this important?

Currently, private repository credentials are managed using secrets, and users can create them declaratively or via Argo CD UI/CLI. The principal should automatically map these repository secrets to the correct agent and sync them to the workload clusters.

Scenarios

1. ...

Other Considerations

Credentials on the control plane need to be project-scoped and must exist in an agent’s namespace. Currently, AppProjects from the control plane are being synced to all the agents. Instead, the AppProject must only be synced to the appropriate agents.

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.