Story (Required)

Currently, AppProjects created on the control plane are synced to all the agents connected to the principal. The argocd components on the workload cluster only need AppProjects that are required for managing Applications on that cluster. So, the principal should map the AppProjects to the correct agents. The principal could make use of destinations and source namespaces from the AppProjects to filter the target agents.
Please go through this document for more details: https://docs.google.com/document/d/1MLq8XCUH_VOKzwExogfMeUoyo_8EIgd6J5iSTibyt64/edit?tab=t.0#heading=h.cbmre4boldkm

This is also a prerequisite to support private repository credentials because we expect the repository credentials to be project-scoped. The principal will use the project to map the repo secrets to the correct agents.

Acceptance Criteria (Mandatory)

• Users should be able to sync the AppProjects on the control plane to the correct workload clusters.

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.