Story (Required)

As a user of GitOps Operator/Argo CD, I want to know how I can integrate Terraform into my workflow in the form of a guide/knowledge article/documentation of some sort. 

Background (Required)

Request arose because of this slack thread https://redhat-internal.slack.com/archives/CMP95ST2N/p1702987739809089  

Out of scope

Any changes to current code are out of scope and should be tracked separately- only ask is to document a guide with current procedures & any limitations.

Approach (Required)

• Add documentation officially (to our docs here https://docs.openshift.com/gitops/1.10/understanding_openshift_gitops/what-is-gitops.html_ 
• Evaluate if upstream argocd documentation could use this (would need to make it agnostic to gitops operator though)
• Add this information to our CEE training in Confluence (https://spaces.redhat.com/display/GITOPS/CEE+Training) 

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

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>

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met