Terraform Repository Best Practices, Part 3

preview_player
Показать описание
This video is the third in our three-part series on Terraform repository best practices.

In this video, Nebulaworks Cloud Engineer, Matthew Ramirez reviews the Terraform code release process. The release process allows our team at Nebulaworks to walk over newly developed infrastructure functionality from our testing environments to stable environments. Matt will cover why you need a release process, and what the process entails.

Links to first and second videos on Terraform repository best practices:

Additional Resources:

Рекомендации по теме
Комментарии
Автор

Great Explanation! I have a couple questions:
1) How do you auto-apply .tf configs using CI/CD? Which branches are set to auto-deploy?
2) Also, do you create a repository for each application team? Is this process simply to create internal modules for an application team? If so, what is the difference in git-branching strategy for creating consumable, external modules for the rest of the enterprise?


Thanks!

flobberg
Автор

For your environments (prod, uat) you are using the filesystem to separate them, have you ever considered using terraform workspaces instead?

andrewkewqc
Автор

You are versioning modules, but not what you have in main.tf. There should be a way to not having to change main.tf manually in each environment because it can cause differences in environments..

JoanPorta