Story (Required)

• As a user trying to run resource actions when using argocd-agent, I want the Argo CD server to execute the actions even if it doesn't have direct access to the k8s resources on the workload cluster.
• Use the existing resource proxy to exchange events between the Argo CD server and the agent
• The proxy should talk to the correct agent and return the required resource from the workload cluster to thr Argo CD server
• Once the Argo CD server runs the resource actions, the proxy must forward the results back to the agent/workload cluster

Background and Approach (Required)

• See Parent EPIC and resource proxy design for more background.

Out of Scope

• N/A

Dependencies

• N/A

Acceptance Criteria

• Users should be able to run both built-in and custom resource actions when using argocd-agent
• Unit tests and e2e tests to verify the behavior
• Required PRs are reviewed and merged in the argocd-agent repository

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.