Convert the application to be Terraform exclusive

[asteel-gsa]

Overview

As part of ongoing discussions, this ticket is detailing the work that would go into making the FAC application available to be brought up in the personal cloud.gov sandbox environments. Part of that work would be removing the deployment from manifest files, and handling the application deployment through terraform.

Supporting Services

Tasks

Beta Give feedback

1. Deploy the fac-db to the sandbox environment
2. Deploy the fac-snapshot-db to the sandbox environment
3. Deploy the fac-public-s3 to the sandbox environment
4. Deploy the fac-private-s3 to the sandbox environment
5. Setup the necessary domains
6. Setup any necessary routing
7. ....

Core Services

Tasks

Beta Give feedback

1. Deploy Postgrest instance to the sandbox environment
2. Deploy the gsa-fac app to the sandbox environment
3. Deploy the proxies to the sandbox environment
4. Deploy clamav to the sandbox environment

We are ommitting the logshipper and anything to do with new relic, as we do not want to be sending sandbox logs to be captured with new relic

Debugging Tasks

Tasks

Beta Give feedback

1. Figure out why the terraform to deploy the proxy isn't working
2. Figure out how to pull the application out of the manifest and deploy with terraform, using the same methodology we use for other services
3. Figure out how to handle the <space>-egress configurations (i.e can the proxy work on internal domain, in the same space as the app)

Closeout Tasks

Tasks

Beta Give feedback

1. Create a readme for how to deploy

[danswick]

The terraform-exclusive configuration is only for Sandbox at this stage.

Next steps: setup WSL for testing on Windows machines (Hassan, Bobby, Alex). README needs to be updated and reviewed. Testing right now is primarily individual workstations.

Possibly blocked by or needs to be coordinated with Matt's API work.

We'll know this phase is done when:

1. @asteel-gsa, are @sambodeme are set up on Windows
2. Update the README and onboarding docs
3. @rnovak338 runs through setup on his own using onboarding docs and asks for help when he gets stuck.
4. Iterate the docs and onboard someone else with the new version.