Story (Required)

• As and OpenShift GitOps User, I want Application Health to be stored in Application CR status field instead of external storage, so that the RHACM topology view can show the health status of the application resources.

Background and Approach (Required)

https://argo-cd.readthedocs.io/en/stable/operator-manual/upgrading/2.14-3.0/#health-status-in-the-application-cr

Out of Scope

• <Defines what is not included in this story.>

Approach

• GitOps Operator has to set the controller.resource.health.persist to true in the Argo CD argocd-cmd-params-cm.yaml Config Map by default to all Argo CD instances that it manages.
• If there is a way to track if user overrode this value, it can be preserved, else overwrite it to true.

Acceptance Criteria (Mandatory)

• <Describe edge cases to consider when implementing the story and defining tests.>
• <Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story.>

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.