Update Deployment Model to Terraform

[arank]

To support multi-cloud deployment we should transition from Cloud formation to Terraform on AWS. This should also include options for what level of access the provisioned IAM creds deployed will allow CUDly to do

[arank]

@crisjermaglasang can you test deployment of the branch with this multi-cloud deployment model https://github.com/LeanerCloud/CUDly/tree/feat/multicloud-web-frontend/terraform/profiles

[arank]

@crisjermaglasang do we have this being deployed in our test environment? I didn't see it in the account

[crisjermaglasang]

@arank Should I use the same AWS test account I used before?

[arank]

Yes write the deployment unit test in the AWS account and Azure account you have access to

[cristim]

We're now in the process of deploying the Terraform code into @crisjermaglasang's dev account.

We noticed a number of issues related to infrastructure code that evolved over time and worked when applying changes on the existing infrastructure but failed to apply when deployed from scratch because some of the configurations were expecting resources to exist from previous runs.

We fixed a few of them in a trial and error manner but that was slow, so I then started to reproduce them locally by destroying/applying the entire application running in my own AWS account and identified a few more that were fixed as well.

Now in the process of doing the same for Azure and GCP Terraform code.

[cristim]

we have working TF code that works across cloud providers from the CI/CD pipeline, and also deployed to @crisjermaglasang's account. I think we can close this issue.