-
Notifications
You must be signed in to change notification settings - Fork 471
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 why this way #25746
Terraform why this way #25746
Conversation
@rfairburn This looks good to me with the suggested edit. I'm tagging @noahtalerman for visibility. Ultimately this will need @mikermcneil's approval, which may take a few days. I'll bring to e-group on Wednesday if it isn't reviewed by then. I'm adding a summary in the PR description explaining why we're making this change. |
Co-authored-by: Luke Heath <[email protected]>
@lukeheath thanks. I committed your recommendation and moved the PR into "Ready for Review" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved by me, will need @mikermcneil's approval as DRI for the page before we create the repo.
@Sampfluger88 Tagging you to get it on your radar. |
Thanks! @rfairburn @zayhanlon |
For #18191
Why add another repo?
Terraform clones the entire repo for every submodule used when running
terraform init
. For our monorepo, that is 11GB, which significantly slows down deployment speed using Terraform. By moving our Terraform modules to a dedicated repo, we reduce this to <1MB, which will shave minutes off ofterraform init
for anyone who uses it. Because our CI deployment runsterraform init
on every environment, this will result in savings of several hours of CI runners per month.