You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Getting the Level I and Level II project access set-up on Ops.
Overview
DevOps needs to complete a migration from Terragrunt to Terraform.
The most important reason being, Terragrunt has been made largely superfluous by
features added to Terraform, and as a result is not well known in the larger Ops community.
Better to be learning and teaching Terraform, which is an industry standard.
More subtly but just as important, Terraform has lots of support in the larger community.
There's lots of tools, documentation, and general experience with Terraform that
Terragrunt simply can't compare to. It's even possible that Hack for LA volunteers
will have existing experience with Terraform and be able to contribute right away.
The general principle here, and moreso that other organizations, is Hack for LA should consider
the available expertise for their tools as a very high priority. In the case of Infrastructure as Code, there are many, many toolsets available, but Terraform is one of a small set of clear winners in terms of broad adoption.
Issues need to be created on each of the above Github repos, and noted here.
Responsible parties for those projects need to be identified and noted here.
Resources/Instructions
A guide to this process can be found in this projects [documentation/] directory.
Please direct questions about this project or requests for aid (which are expected!) to the #ops channel - feel free to ping @judson(github: @nyarly) or @JasonEb
The text was updated successfully, but these errors were encountered:
Dependency
Overview
DevOps needs to complete a migration from Terragrunt to Terraform.
The most important reason being, Terragrunt has been made largely superfluous by
features added to Terraform, and as a result is not well known in the larger Ops community.
Better to be learning and teaching Terraform, which is an industry standard.
More subtly but just as important, Terraform has lots of support in the larger community.
There's lots of tools, documentation, and general experience with Terraform that
Terragrunt simply can't compare to. It's even possible that Hack for LA volunteers
will have existing experience with Terraform and be able to contribute right away.
The general principle here, and moreso that other organizations, is Hack for LA should consider
the available expertise for their tools as a very high priority. In the case of Infrastructure as Code, there are many, many toolsets available, but Terraform is one of a small set of clear winners in terms of broad adoption.
This process has already started (c.f. https://github.com/hackforla/incubator/blob/main/documentation/terraform-migrate-project.md),
but the approach used for Terragrunt means that project owners need to help contribute to the migration process. In particular, there are
project.hcl
files that have been used to store secret data, and are managed by the owners of particular projects.Action Items
The following projects need to be migrated:
Assist with migrating deployment to Terraform HomeUniteUs#585Resources/Instructions
A guide to this process can be found in this projects [documentation/] directory.
Please direct questions about this project or requests for aid (which are expected!) to the #ops channel - feel free to ping @judson(github: @nyarly) or @JasonEb
The text was updated successfully, but these errors were encountered: