Background

There is currently a need to "GitOps-ify" traditional Infrastructure as Code providers. Currently, Flux has a controller called the Terraform Controller for Flux.

This controller is quite popular, so much so that folks are asking for it in the Argo CD slack channels on the CNCF. Which Flux's answer is to use the Flux Subsystem for Argo controller.

User Story

As an end user, I would like to use Argo CD to manage my Ansible Playbooks and my Terraform scripts, so that I can use a GitOps workflow to manage resources managed by those IaC providers.

Ideal Acceptance Criteria

Have a new project in argoproj-labs called "argocd-iac-controller" that provides functionality to Argo CD that let's it manage Ansible Playbooks and Terraform Scripts. It will do this with new CRDs that provide the group/version of "infra.argoproj.io/v1alpha1" and kinds of "terraforms" and "ansiblePlaybooks". The controllers will pull playbooks and terraform scripts sources from Git.

Notes

ablock@redhat.com, sde-rcook, Joseph Sawaya (ex-Red Hat intern), and Myself started https://github.com/sabre1041/argocd-terraform-controller that can be used as a starting point/POC.