words.md

Table of Contents

• 1. Terraform tfstate
  • 1.1. #1 Terraform Init
  • 1.2. #2 Terraform Plan
  • 1.3. #3 Terraform Apply
  • 1.4. #4 Terraform Plan
  • 1.5. #5 Change the file .terraform/terraform.tfstate
    • 1.5.1. Before Change It
    • 1.5.2. After Change it
    • 1.5.3. Difference
  • 1.6. #6 Terraform Plan

Terraform tfstate

#1 Terraform Init

❯ ~/git/terraform/bin/terraform init                                   

Initializing the backend...

Initializing provider plugins...

The following providers do not have any version constraints in configuration,
so the latest version was installed.

To prevent automatic upgrades to new major versions that may contain breaking
changes, it is recommended to add version = "..." constraints to the
corresponding provider blocks in configuration, with the constraint strings
suggested below.

 * provider.aws: version = "~> 0.1"

Terraform has been successfully initialized!

You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.

If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.

#2 Terraform Plan

❯ ~/git/terraform/bin/terraform plan 
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.

+ aws_s3_bucket.w
    acceleration_status: "<computed>"
    acl:                 "private"
    arn:                 "<computed>"
    bucket:              "my_tf_test_bucket_w"
    bucket_domain_name:  "<computed>"
    force_destroy:       "false"
    hosted_zone_id:      "<computed>"
    region:              "<computed>"
    request_payer:       "<computed>"
    tags.%:              "2"
    tags.Environment:    "Dev"
    tags.Name:           "My bucket name"
    versioning.#:        "<computed>"
    website_domain:      "<computed>"
    website_endpoint:    "<computed>"


Plan: 1 to add, 0 to change, 0 to destroy.

#3 Terraform Apply

❯ ~/git/terraform/bin/terraform apply  
aws_s3_bucket.w: Creating...
  acceleration_status: "" => "<computed>"
  acl:                 "" => "private"
  arn:                 "" => "<computed>"
  bucket:              "" => "my_tf_test_bucket_w"
  bucket_domain_name:  "" => "<computed>"
  force_destroy:       "" => "false"
  hosted_zone_id:      "" => "<computed>"
  region:              "" => "<computed>"
  request_payer:       "" => "<computed>"
  tags.%:              "" => "2"
  tags.Environment:    "" => "Dev"
  tags.Name:           "" => "My bucket name"
  versioning.#:        "" => "<computed>"
  website_domain:      "" => "<computed>"
  website_endpoint:    "" => "<computed>"
aws_s3_bucket.w: Still creating... (10s elapsed)
aws_s3_bucket.w: Still creating... (20s elapsed)
aws_s3_bucket.w: Still creating... (30s elapsed)
aws_s3_bucket.w: Creation complete (ID: my_tf_test_bucket_w)

Apply complete! Resources: 1 added, 0 changed, 0 destroyed.

The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the `terraform show` command.

State path:

#4 Terraform Plan

❯ ~/git/terraform/bin/terraform plan
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

aws_s3_bucket.w: Refreshing state... (ID: my_tf_test_bucket_w)
No changes. Infrastructure is up-to-date.

This means that Terraform did not detect any differences between your
configuration and real physical resources that exist. As a result, Terraform
doesn't need to do anything.

#5 Change the file .terraform/terraform.tfstate

Before Change It

    {
        "version": 3,
        "serial": 0,
        "lineage": "15b3c30a-628a-4afe-84ec-9dedbd0c3f38",
        "backend": {
            "type": "s3",
            "config": {
                "bucket": "walter-devops-us-east-1",
                "encrypt": true,
                "key": "terraform/dev/terraform.tfstate",
                "region": "us-east-1"
            },
            "hash": 15754410838997573272
        },
        "modules": [
            {
                "path": [
                    "root"
                ],
                "outputs": {},
                "resources": {},
                "depends_on": []
            }
        ]
    }

After Change it

    {
        "version": 3,
        "serial": 0,
        "lineage": "15b3c30a-628a-4afe-84ec-9dedbd0c3f38",
        "backend": {
            "type": "s3",
            "config": {
                "bucket": "walter-devops-us-east-1",
                "encrypt": true,
                "key": "terraform/prod/terraform.tfstate",
                "region": "us-east-1"
            },
            "hash": 15754410838997573272
        },
        "modules": [
            {
                "path": [
                    "root"
                ],
                "outputs": {},
                "resources": {},
                "depends_on": []
            }
        ]
    }

Difference

    10c10
    <             "key": "terraform/dev/terraform.tfstate",
    ---
    >             "key": "terraform/prod/terraform.tfstate",

#6 Terraform Plan

~/git/terraform/bin/terraform plan

~/git/terraform-state/s3 master*
❯ ~/git/terraform/bin/terraform plan 
Refreshing Terraform state in-memory prior to plan...
The refreshed state will be used to calculate this plan, but will not be
persisted to local or remote state storage.

The Terraform execution plan has been generated and is shown below.
Resources are shown in alphabetical order for quick scanning. Green resources
will be created (or destroyed and then created if an existing resource
exists), yellow resources are being changed in-place, and red resources
will be destroyed. Cyan entries are data sources to be read.

Note: You didn't specify an "-out" parameter to save this plan, so when
"apply" is called, Terraform can't guarantee this is what will execute.

+ aws_s3_bucket.w
    acceleration_status: "<computed>"
    acl:                 "private"
    arn:                 "<computed>"
    bucket:              "my_tf_test_bucket_w"
    bucket_domain_name:  "<computed>"
    force_destroy:       "false"
    hosted_zone_id:      "<computed>"
    region:              "<computed>"
    request_payer:       "<computed>"
    tags.%:              "2"
    tags.Environment:    "Dev"
    tags.Name:           "My bucket name"
    versioning.#:        "<computed>"
    website_domain:      "<computed>"
    website_endpoint:    "<computed>"


Plan: 1 to add, 0 to change, 0 to destroy.