Terraform Enterprise Azure Demo

In this video, we explain how to deploy infrastructure into Azure using Terraform Cloud/Enterprise.
We also explain how Terraform works and the workflow for using a version control system (VCS) or a CI/CD workflow.
Connect VCS to Terraform Enterprise and trigger automatic runs based on commits and pushes.
Sentinel = Policy as Code to create guardrails as you provision infrastructure.
▬▬▬▬▬▬▬▬▬ Courses 🎓 ▬▬▬▬▬▬▬▬
- TeKanAid Academy Subscription ► bit.ly/subscription-premium
- Terraform 101 - Certified Terraform Associate ► bit.ly/hc-terraform-101
🎟️ Get 15% off of my Terraform 101 Course with this coupon ► TH-cam15TF101
- HashiCorp Sentinel 101 ► bit.ly/hc-sentinel-101
- HashiCorp Vault 101 - Certified Vault Associate ► bit.ly/hc-vault101
🎟️ Get 15% off of my Vault 101 Course with this coupon ► TH-cam15VAULT101
- HashiCorp Vault 201 - Vault for Apps in Kubernetes ► bit.ly/hc-vault-201
GitHub Repos:
github.com/samgabrail/hashica...
github.com/samgabrail/hashica...
github.com/samgabrail/tfe_policy

[@samys288]

Thank you Sam, excellent video! I would like ask you 2 questions; 1. what is your advised; create new modules into of TFC or using the terraform public modules? 2. The terraform enterprise self-hosted instance in which use case must be used instead of TFC?

[@TeKanAid]

1. Using New Modules vs Terraform Public Modules in Terraform Cloud (TFC):
Pros of Creating New Modules: When you create your own modules, you have complete control over the functionality and can tailor them exactly to your specific needs. This can be particularly useful if you have unique requirements or if you're working in a highly specialized environment. Plus, developing your own modules can deepen your understanding of Terraform.
Pros of Using Terraform Public Modules: These modules are often well-tested and widely used, meaning they're generally reliable and efficient. Using public modules can save you a lot of time and effort, especially for common infrastructure patterns. It's a great way to leverage the community's knowledge and avoid reinventing the wheel.
My Advice: Assess your needs. If your requirements are fairly standard and covered by existing public modules, go for those. They’re time-savers. But, if you have specific needs or want to implement unique configurations, creating your own modules might be the way to go.
2. Terraform Enterprise Self-Hosted vs Terraform Cloud (TFC):
Use Cases for Terraform Enterprise Self-Hosted:
Regulatory Compliance and Data Control: If your organization has strict compliance requirements or needs to keep data within its own data centers for security reasons, a self-hosted instance is a good fit.
Customization Needs: Some organizations require a higher level of customization than what is available in TFC. Self-hosting allows for more control over the environment.
Network Restrictions: If your infrastructure is in a network that cannot be easily accessed from the cloud (like a private data center with strict firewall rules), a self-hosted Terraform Enterprise can operate within your network.
Terraform Cloud (TFC):
It's generally a good choice for teams that don’t have the above constraints. TFC is easy to set up and manage, making it suitable for a wide range of applications.

[@samys288]

@@TeKanAidThank you very much!

[@TeKanAid]

@@samys288 you are most welcome!

[@shahkerali]

Its very helpful

[@TeKanAid]

Glad to hear that

[@abcdanybodycando--coding]

Nice one. I am just start doing learning terraform enterprise. this is nice video. One quick question variable = tfvars equivalent or envrionment variables = tfvars ? What is main difference between variables and enviornment variables ?

[@TeKanAid]

Thanks. Variables are terraform variables that you would define in a tfvars in OSS. Since Terraform Enterprise runs either on the cloud or on self hosted servers, you can also define environment variables for the system where terraform will run. Hope this helps.

[@abcdanybodycando--coding]

@@TeKanAid Thanks for explanation. what I observed is while creating terraform variable which should match my variables.tf when I select HCL checkin box then it errored out saying you cannot use variable here. then i unchecked the HCL check box then it substituted at runtime, but HCL box tool tip says use it when your need interpolation(i mean variable substitution) not sure what is purpose of that HCL checkbox there. Where can i configure Plan or apply with define -var or var-file as parameter ?

[@TeKanAid]

@@abcdanybodycando--coding check this article that has some good details on variables www.terraform.io/cloud-docs/workspaces/variables. Also it depends on what workflow you're using. The CLI workflow is the closest to OSS check this article also www.terraform.io/cloud-docs/run/cli

[@parvathygireendran1004]

Hi . Do you have terraform enterprise on GCP video?

[@TeKanAid]

Sorry, not yet, but I can add it to the list of videos to create.

[@yuvrajjambhle9061]

Hi, nice video. I wanted to know how terraform import execute in terraform enterprise? Actually I have created RDS instance manually in aws now I want to apply the terraform code but getting an error like "Error creating DB instance : DB Instance Already Exists: DB instance already exists ; status code : 400". I want to update it in terraform code

[@TeKanAid]

There is a new Terraform import block instead of using the Terraform import Cli command. Check out the docs for importing here. developer.hashicorp.com/terraform/cli/import

[@yuvrajjambhle9061]

@@TeKanAid Hi, it not works, got an error like Error: Unsupported block type, block of type "import" are not expected here.

[@TeKanAid]

@@yuvrajjambhle9061 Terraform v1.5.0 and later supports import blocks.

[@MrSubhoece]

Thanks for the nice explanation. Can you please share the github repo of the code please. Will be very helpful

[@TeKanAid]

Thank you, I just shared the repos in the description of the video.

[@MrSubhoece]

@@TeKanAid great thanks