Assist with migrating deployment to Terraform

[nyarly]

Dependency

• Add specific dependency here that must be met in order to move the issue to the prioritized backlog

Overview

Hello there!

The Ops team is changing the way we deploy applications in Incubator, and we need the help of someone on this project to accomplish that. Thanks in advance!

There was a project.hcl file created and edited by a member of this project at one point - they'll need to be the one to participate.

Action Items

There's an epic issue that describes the overall process: hackforla/incubator#20

Please follow the guide there to effect the Terraform migration of this project's deployment!

Resources/Instructions

The Issue above has all the details you should need. We're using it as a central clearinghouse, so we'll updating it with any new information or clarifications so that we can help everybody.

Please reach out to @nyarly (@judson on slack) or @JasonEb (same handle) with any questions.

[JackHaeg]

@jbubar & @spiteless please look into this.

[JackHaeg]

@nyarly & @JasonEb Can you please provide an estimated time commitment so that we can size the issue appropriately?

[nyarly]

Estimate a couple of hours, I think

[ExperimentsInHonesty]

@Tyson-miller Please provide update

1. Progress: "What is the current status of your project? What have you completed and what is left to do?"
2. Blockers: "Difficulties or errors encountered."
3. Availability: "How much time will you have this week to work on this issue?"
4. ETA: "When do you expect this issue to be completed?"
5. Pictures or links* (if necessary): "Add any pictures or links that will help illustrate what you are working on."

• remember to add links to the top of the issue if they are going to be needed again.

[Tyson-miller]

Update:

1. 2 PRs are up ready for review
   • Migrating vrms-backend to terraform incubator#28
   • Vrms client terraform migration incubator#29
2. Not necessarily a blocker but I created an issue to refresh the secrets exposed in the PR for vrms-backend which should get done at some point.
3. Probably 3-4 hours
4. I feel it's ready pending PR approvals

[JackHaeg]

@spiteless PRs to check out (discussed on Feb 5 All team mtg)

[JackHaeg]

@spiteless Tagging again to review these PRs and/or coordinate with existing reviewers to implement next steps.

[JackHaeg]

@jbubar & @chelseybeck discussed and will work on together.

[sudhara]

chelsey will review the hcl files that are located in the VRMS vault of 1password. @chelseybeck

[angela-lee1]

Per the discussion at the 11/13 Ops meeting, this issue will be placed in the icebox due to dependencies and other complexities.
@JackHaeg @chelseybeck @ale210

[JackHaeg]

@angela-lee1 @chelseybeck & @ale210 If you have additional information about the dependencies that must be met in order to move this issue out of the icebox and into the prioritized backlog, please add these dependencies as a comment on this issue.

Also, please note that @angela-lee1 will be doing another commit to refresh the PR.

[angela-lee1]

I was unable to make another commit to refresh the PR due to branch protection. Could you disable branch protection temporarily? Could we close and reopen PR #29 to trigger the GitHub Action? If needed, I can also create a temporary PR.
@JackHaeg @chelseybeck @ale210