Terraform Workspaces | Keeping environments separated

preview_player
Показать описание
Should you be using terraform workspaces? How can I separate out my environment deployments? These are questions you may have when looking to start getting into deploying environments across different cloud providers using terraform.

This video goes over a simple overview on the small advantages of using terraform workspaces. Terraform workspaces allow for you to keep separate state files across your deployments using the same code.

Follow along and watch how to keep that structure in place using the terraform cli.

ABOUT OUR CHANNEL: My channel covers various topics about networking, automation and cloud technologies . We cover lots of cool stuff such as cisco, terraform, aws, firewalls, security and more

Don’t forget to subscribe!

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

Great work Kev, clear cut and to the point!

marctatum
Автор

Thank you for posting this. in addition separating tfvars into separate folders, is there a way to do that for resources as well? for instance, you may have applications in dev or stage but do not want them in production until you are ready and it may be a subset of applications from what is in stage or dev. so, looking to keep some common things like provider and some base config centralized (DRY) but also that the option to point to other resources. thanks

JohnSchwartz-ryev
Автор

Hi. Great video! Do companies use this method to create different environments? Would like to see how this can be automated for resource creation etc. using Azure DevOps yaml pipelines. Thanks

marsamuk