kovagoadi/hunfabric
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix pre-commit hook (#3882)

Browse Source
This commit is contained in:
Luca Prete
2026-04-18 10:07:14 +02:00
committed by GitHub
parent 7a31a07df9
commit f2d4e937d1
286 changed files with 295 additions and 449 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
FABRIC-AND-CFT.md
View File

@@ -140,7 +140,7 @@ For production/airgapped usage, customers may also mirror modules to a private r
## Should you choose Fabric or CFT?
> You/Your organization is knowledgeable in Terraform and interested in forking and owning a collection of modules.
Fabric is a better choice as it bootstraps you with a collection of modules out of the box that can be customized exactly to fit your organization needs.
> You/Your organization is getting started with Terraform and interested in GCP best practices out of the box.
@@ -148,11 +148,11 @@ For production/airgapped usage, customers may also mirror modules to a private r
CFT is a better choice as it allows you to directly reference specific modules from the registry and provide opinionated configuration by default.
> You/Your organization is looking to rapidly prototype some functionality on GCP.
Fabric is a better choice. Being a mono repo it allows you to get started quickly with all your source code in one place for easier debugging.
> You/Your organization has existing infrastructure and processes but want to start adopting IaC gradually.
CFT is designed to be modular and off the shelf, providing higher level abstractions to product groups which allows certain teams to adopt Terraform without maintenance burden while allowing others to follow existing practices.
## Using Fabric and CFT together