Value Statement

Currently, Argo CD Agent uses gRPC for communication between the spoke and hub components. While this works, it may limit scalability and flexibility. Maestro supports message queue technologies, which could offer improved scalability. By introducing an interface layer in Argo CD Agent:

• gRPC remains the default (gRPC will also adopt the new interface).
• Maestro can be plugged in as an alternative, leveraging its messaging capabilities.
• This creates an opportunity to further tightly integrate ACM with OpenShift GitOps.

Definition of Done for Engineering Story Owner (Checklist)

•  Validated the feasibility of this design.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.