Value Statement

ArgoCD Pull Model needs to propagate the hub Application's "operation" field to the managed cluster to support manual and AppSet progressive sync.

Definition of Done for Engineering Story Owner (Checklist)

• When using the pull model if the dormant hub Application has an "operation" field then the ArgoCD pull integration propagation controller should wrap the Application CR with the "operation" field as well.
• Currently the "operation" field is ignored because it's not under the "spec". The "operation" field is unique to ArgoCD Application CR that is at the same level as the "spec" and "status.

• An example of an operation field inserted by AppSet controller:

  operation:
    info:
    - name: Reason
      value: ApplicationSet RollingSync triggered a sync of this Application resource.
    initiatedBy:
      automated: true
      username: applicationset-controller
    retry: {}
    sync:
      syncOptions:
      - CreateNamespace=true 

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 template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

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