TERRAFORM

Keywords:
Provider count
resource dynamic_block
output for_each
TERRAFORM -- Open source software for variable depends_ons
defining and provisioning a datacenter
infrastructure using configuration files
data
Meta Parametre:
Length look-up
element join
file cidr subnet

1. By using terraform we can automate multiple cloud.

Terraform life cycle
2. By using provider keword terraform will identify which cloud
provider it need to connect.
3. Once we mention the provider details we need to download the
plug-ins.
4. By using terraform-init command, we can download the plug-ins
5. After that we can create the resources like (vpc, instances,
RT,IGW)
based on the requirement we can create the resources.
----> Provider
----> Resource
----> variable
----> output

Types of provisioners:
Provisioners - can be execute at 1. File -- copy file from terraform machine to remote (any)
resource creation machine
2. Connection
Null resource -- dummy resource but 3. remote execution -- accessing the remote machine from my
have all the properties of all resource machine.
(eg: resource "null" "nrl") 4. local execution

Commands terraform init,

Terraform module (usually the root module of a configuration) can
call other modules to include their resources into the
Terraform module
configuration. A module that has been called by another module is
often referred to as a child module.
workspaces wach have state files. Will have isolated or
independednt different environments like development, staging
Terraform workspace
and production for each workspace. This separation helps to
manage large deployments

A backend defines where terraform stores its state data files.

Terraform backend
This lets multiple people access the state data and work together
on that collection of infrastructure resources. (backend like s3..)