Elgato_dark/fleet
1
0
Fork 0
mirror of https://github.com/fleetdm/fleet synced 2026-05-23 17:08:53 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 83

Terraform why this way (#25746)

Browse source 
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 of `terraform init` for anyone who uses it. Because our CI
deployment runs `terraform init` on every environment, this will result
in savings of several hours of CI runners per month.

---------

Co-authored-by: Luke Heath <luke@fleetdm.com>
This commit is contained in:
Robert Fairburn 2025-01-27 12:09:17 -06:00 committed by GitHub
parent 8ee29dc895
commit de46eb31d8
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
handbook/company/why-this-way.md
View file

@ -132,6 +132,7 @@ The only exceptions are:
4. **Software vulnerabilities:** Since GitHub only allows one latest release per repository, we currently maintain two repositories to host our CVE/CPE database releases:
- _vulnerabilities:_ [`fleetdm/vulnerabilities`](https://github.com/fleetdm/vulnerabilities)
- _nvd:_ [`fleetdm/nvd`](https://github.com/fleetdm/nvd)
5. **Terraform modules:** Since Terraform clones the entire repo once per tagged version of a module, we maintain a separate repo for Terraform modules at [fleetdm/fleet-terraform](https://github.com/fleetdm/fleet-terraform) to expedite deployments using `terraform init`.
Besides the exceptions above, Fleet does not use any other repositories. Other GitHub repositories in `fleetdm` should be archived and made private.