Closed lsetiawan closed 3 years ago
Using terragrunt will also protect the terraform state by using a dynamodb state lock table, that way updating infrastructure can be more collaborative and protect from overwriting state.
With terragrunt, one can go to the root terraform
folder and execute all the various modules in one place.
terragrunt run-all init
terragrunt run-all plan
This will look into the setup/ami
and eks
sub directory.
wow! this looks great @lsetiawan, thanks so much for improving things! I really like the organization, i noticed that I was repeating things like the backend specification and that a cleaner organization was possible. i haven't used terragrunt before, but it seems like a valuable addition here.
protect the terraform state by using a dynamodb state lock table
in the past we had things set up this way, but my thought was that if we force all updates to go through github this would likely be a non-issue. certainly doesn't hurt though, and is probably best practice.
merge away!
Overview
This PR will initialize the use of terragrunt: https://terragrunt.gruntwork.io/
This will help with the setup of the jupyterhub infrastructure to be more DRY :smile: