Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Terraform Script for MDF Connect #77

Open
BenGalewsky opened this issue Mar 15, 2023 · 11 comments
Open

Terraform Script for MDF Connect #77

BenGalewsky opened this issue Mar 15, 2023 · 11 comments
Assignees
Labels
v-Automate first version on MDF roadmap

Comments

@BenGalewsky
Copy link
Contributor

BenGalewsky commented Mar 15, 2023

As an MDF developer I want to be able to deploy instance of server using Terraform so I can easily reproduce my environment

Description

Should be based on terraform scripts created for garden

We should attempt to namespace the resources so it's easy to view only MDF or only Garden resources

Here is the miro board that shows the architecture

@ascourtas
Copy link

@BenGalewsky whenever you get a chance, can you flesh out this story a little more so Steve or Eric can pick it up?

@ericblau
Copy link
Contributor

ericblau commented Apr 5, 2023

I've picked this up, and have been looking at Will's terraform code, and sketching out what this will need.

@ericblau
Copy link
Contributor

ericblau commented May 2, 2023

I now have a full outline of terraform code to create an aws apigatewayv2 with a submit and a status endpoint, with three stages, "Development", Testing" and "Production", and the lambdas that implement the endpoints, all in an "MDF Connect" namespace. Left: get it all debugged and working.

@ascourtas ascourtas added the v-Automate first version on MDF roadmap label Jun 13, 2023
@ascourtas
Copy link

Eric working through final issues -- it's close, just a few weird things that need to be resolved. Hoping to be done this afternoon. Aiming to be totally done before leaving for vaca on Thursday

@blaiszik
Copy link
Contributor

How is this going @ericblau?

@ericblau
Copy link
Contributor

First pass of the infrastructure is up in place. The lambdas need to be deployed into it and tested to confirm happiness--it is certainly possible that tweaks will need to be made. In the meantime, BenG proposed that we might want to look at deploying the lambdas as containers instead of layers: #84

@ericblau
Copy link
Contributor

Terraform code for both lambdas with layers and lambdas defined by containers has been written. I'm going to block this until we can evaluate them

@ericblau
Copy link
Contributor

I'm unblocking this and putting it back "in progress", and just subsuming #84 as part of this--esp. because I can't figure out how to add it to the sprint on its own. Status: container infra has been defined, need to deploy to it and decide which direction to go.

@ericblau
Copy link
Contributor

ericblau commented Aug 1, 2023

Still working on #84, a little stuck bootstrapping the containers for the lambdas-deployed-as-containers infrastructure to deploy.

@ericblau
Copy link
Contributor

Marking this as blocked on #84

@ericblau
Copy link
Contributor

This is finished, and in the MDF connect_server repo in infra/mdf/.
The terraform deployment creates the infrastructure for the auth, submit, and status functions, in both prod and test, and http_api gateways for test and prod. (The MDF-Connect namespace and the deployed envs (prod and test) are redefinable if additional deployments are desired, with different names). It also defines a role that can be assumed by github actions to update the lambda code.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
v-Automate first version on MDF roadmap
Projects
None yet
Development

No branches or pull requests

5 participants