Terraform is an open-source platform for building, changing, and maintaining infrastructure such as servers. This post will walk through deploying a new instance with Terraform.
“terraform output to variable” is a tool that allows you to take the output of terraform and store it in a variable. This gives you the ability to use the same template for multiple different instances of your project.
If you’re using Terraform to develop a large infrastructure, numerous Terraform Workspaces are essential. A Terraform workspace is a virtual place where you may store your persistent data.
You’ll discover how Terraform workspace allows team members or developers to work on code without affecting current resources in this lesson.
Isn’t it intriguing? Continue reading!
Prerequisites
If you want to follow along with this lesson, make sure you have the following:
How to Install Terraform on Windows is a related topic.
- A code editor — While you may work with Terraform configuration files with any text editor, you should have one that understands the HCL Terraform language. Visual Studio (VS) Code is a good place to start.
A Tutorial on What You Need to Know About Visual Studio Code
Using Terraform to Create Multiple Workspaces
Engineers like Terraform developers require several workspaces to test the same scripts and code before constructing rock-solid resources in today’s automated age.
Multiple workspaces are now supported by AzureRM, Consul, COS, GCS, Kubernetes, Local, Manta, Postgres, Remote, and S3.
Create two separate workspaces to better understand how multiple Terraform workspaces work:
1. Run the commands below in your terminal to create a folder in your home directory and change the working directory to it.
The folder in this tutorial is named terraform-workspace-demo and is located in your home directory. You may give the folder any name you choose. Your Terraform configuration files are kept in this folder.
mkdir /terraform-workspace-demo/terraform-workspace-demo/terraform-workspace-demo/terraform-work cd /terraform-workspace-demo/terraform-workspace-demo/terraform-workspace-demo/terraform-
2. Open your preferred code editor and put the command below into it.
The terraform workspace new command creates a new workspace (workspace1) and moves your existing workspace to it.
The workspace in this example is called workspace1, but you may call it anything you like.
# Creating and transitioning to a new workspace, workspace1. new workspace1 terraform terraform terraform terraform terraform terraform
Creating and transitioning to a new workspace (workspace1)
Maybe you’d want to go from one workplace to another. If that’s the case, use the command below. Workspace-name should be replaced with the real workspace name. terraform work environment choose a workspace name
3. Run the command below to create a new workspace in the same way. You’ll establish a new workspace called workspace2 this time.
# Creating a new work environment and transitioning to workspace2. new workspace2 terraform terraform terraform terraform terraform terraform
You successfully established and switched to workspace2 as shown below.
Creating and transitioning to a new workspace (workspace2).
If you’d rather, perform the terraform workspace delete workspace-name command to get rid of a workspace you don’t need.
Launching EC2 Instances using Terraform Configurations
You now have two Terraform workspaces in which to work with the identical Terraform settings, but an instance must still be created. In two independent workspaces, you’ll construct the terraform configuration file for an AWS EC2 instance.
1. Copy/paste the settings below into your preferred code editor. Save the configuration as main.tf in the /terraform-workspace-demo/terraform-workspace-demo/terraform-workspace-demo/terraform-workspace-demo/terraform-workspace
Terraform makes use of a variety of configuration files. Each file is saved in plain text or JSON format, with a name convention of.tf or.tfjson.
With the AMI and [instance type] defined as variables in the main.tf file, you may create AWS EC2 instances. The values for these variables are specified in a separate file called terraform.tfvars, which you’ll create later in this section.
The Amazon EC2 console is where you’ll locate Linux AMIs.
# Declaring the argument ami ami = var.ami resource “aws instance” “my-machine” # Declaring the resource block aws instance resource “aws instance” “my-machine” # Declaring the resource block aws instance resource “aws instance” “my-machine” instance type = var.instance type # Declaring the parameter instance type Tags = Name = “ec2-instance-$terraform.workspace” # Tagging the instances tags = “ec2-instance-$terraform.workspace”
2. Now, within the /terraform-workspace-demo directory, create a new file called vars.tf and copy/paste the text below into it. The vars.tf file is a Terraform variables file that includes all of the variables referenced in the configuration file.
# ami variable “ami” variable “ami” variable “ami” variable “ami” variable “ami” variable “ami” variable “ami” variable “ami” var type = string var type = string var type = string var type = string # Creating a Variable for the instance type variable “instance type” # Creating a Variable for the instance type variable “instance type” var type = string var type = string var type = string var type = string
3. Inside the /terraform-workspace-demo directory, create a new file named provider.tf and paste the code below into it. The AWS provider is defined in the provider.tf file, which allows Terraform to connect to the appropriate cloud services.
It is possible to include all configuration settings in a single configuration file. However, splitting the logic and variables into distinct files is much preferred to make things simple for developers and administrators.
Getting Started with the Terraform AWS Provider is related.
The code below generates resources in the us-east-2 region using the AWS provider aws.
AWS resources may be launched in any location.
region = “us-east-2” provider “aws”
4. In the /terraform-workspace-demo directory, create one last file. Create a new file called terraform.tfvars and put the code below into it. Terraform utilizes the values in terraform.tfvars to replace variable references inside a configuration file.
instance type = “t2.micro” ami = “ami-0742a572c2ce45ebf”
5. Finally, run the tree command to ensure that the terraform-workspace-demo folder has all of the essential files.
terraform-workspace-demo tree
Another directory (terraform.tfstate.d) has two directories, as seen below (workspace1 and workspace2). When you build a Terraform workspace, Terraform produces these folders for you.
Verifying the Terraform workspace’s needed folder structure
Using AWS EC2 to Create Two Instances in Different Workspaces
Now that you’ve created the Terraform workspaces and Terraform configuration files, it’s time to start launching AWS EC2 instances. Within two different workspaces, you’ll create and launch two AWS instances.
1. Before you add resources in your AWS account, use the command below to test the Terraform workspace.
# The current workspace terraform workspace show is shown.
The current workspace is workspace2, as seen below.
The current workspace is shown.
2. Navigate to the terraform-workspace-demo directory and initialize Terraform using the commands shown below. Terraform sets up the necessary plugins and providers to deal with resources.
Terraform usually follows a three-step process: terraform init, terraform plan, and terraform apply.
cd terraform-workspace-demo/terraform-workspace-demo/terraform-workspace-demo/terraform ## Terraform init ## Provides an overview of which resources in your infrastructure will be provided terraform plan ## Tells Terraform to provision the instance terraform apply
Creating an AWS EKS Cluster using a Terraform Configuration is related.
If everything goes as planned after performing the terraform apply command, you’ll see the Apply complete! 1 message was added, 0 messages were modified, and 0 messages were deleted.
You’ll need the output instance IDs later to check whether they exist in the AWS Management Console. The program shows the output’s EC2 instance ID as shown below.’
In Workspace2, create an AWS instance.
3. Now execute the command below to switch workspaces from workspace2 to workspace1. Replace workspace-name with the name of the workspace you wish to replace.
pick workspace-name in terraform workspace
Change the workspace from workspace 2 to workspace 1.
Finally, perform the instructions listed below in the same order as before (step two). Terraform builds the instance in a new workspace this time (workspace1).
In Workspace1, create an AWS instance.
In the AWS Console, double-check that the resources exist.
You should have produced all of the Terraform-launched EC2 instances by now. However, you may manually check in the AWS Management Console to see whether all of the EC2 instances exist.
1. Go to the AWS Management Console using your preferred web browser.
2. Now, go to the top of the page and type in ‘EC2’, then choose the EC2 menu item from the drop-down menu.
Getting started with an EC2 console.
Finally, on the EC2 page, verify that all IDs are the same ones that Terraform returned earlier under the “Using AWS EC2 to Create Two Instances in Different Workspaces” section.
In the AWS interface, I’m checking all of the instances.
Conclusion
You learnt how to utilize Terraform workspace to launch many resources using the same Terraform configuration in this article. You may now work on many workspaces without causing havoc!
Take everything you’ve learnt and apply it to managing your whole infrastructure using Terraform!
Related Tags
- terraform azure devops
- the-automator
