Bring your own modules, Terragen wants to as much as possible stay out of your working modules.To ease the pain on the above I wrote Terragen, a pip installable python utility that provides a powerful but lightweight configuration engine ontop of your existing Terraform modules. Let’s see it in action: There can be a lot of boilerplate config files.Establishing enterprise standards, like tags that should be attached to all instances, shared Security Groups and so on can be difficult.Configuration changes between environments, eg TEST environment runs t3.small instances but prod runs m5.xlarge can be cumbersome.The management of shared infra (eg VPCs, Databases) and app level infra in the same repo can be tricky. Eg I definitely don’t want to accidentally tear down a shared database when I’m tearing down my little hello-world app. Managing infrastructure across multiple accounts, eg DEV/TEST/PROD can be painful and can lead to duplication without careful thought.However, it does have its wrinkles, my personal top 5 annoyances I’ve been working with Terraform off and on for around 4 years now. Generally I love it, it’s a powerful tool for managing your cloud based infrastructure and the HCL definition language makes your Infrastructure-as-Code files reasonably readable and maintainable. Terragen provides a simple way to configure sophisticated cloud architectures across multiple accounts
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |