Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefer the json output from terraform version #99

Merged
merged 4 commits into from
Sep 28, 2021
Merged

Conversation

dflook
Copy link
Owner

@dflook dflook commented Sep 25, 2021

No description provided.

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triggering pull_request_review event...

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for pull_request_target

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + output_string = "the_string"

Plan applied in pull_request_target test #92

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for SSH Module

Changes to Outputs
Changes to Outputs:
  + word = "hello"

You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.

Plan applied in Test SSH Keys #85

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_11

Plan: 1 to add, 0 to change, 0 to destroy.
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

+ random_string.my_string
      id:          <computed>
      length:      "11"
      lower:       "true"
      min_lower:   "0"
      min_numeric: "0"
      min_special: "0"
      min_upper:   "0"
      number:      "true"
      result:      <computed>
      special:     "true"
      upper:       "true"
Plan: 1 to add, 0 to change, 0 to destroy.

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_12

Plan: 1 to add, 0 to change, 0 to destroy.
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_15

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = "string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/no_changes

No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_13

Plan: 1 to add, 0 to change, 0 to destroy.
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_14

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = "string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = "string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/error

Error: Incorrect attribute value type
Error: Incorrect attribute value type

  on main.tf line 2, in resource "random_string" "my_string":
   2:   length      = "ten"

Inappropriate value for attribute "length": a number is required.

Failed to generate plan in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/vars
With var files: tests/apply/test.tfvars
With variables: my_var="single"

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + complex_output = "8300:8300:tcp"
  + from_var       = "single"
  + from_varfile   = "monkey"
  + output_string  = "the_string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/plan/plan_15_4

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = "string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Multiple registries

Changes to Outputs
Changes to Outputs:
  + word = "hello"

You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.

Plan applied in Test registry #33

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Optional path

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = "string"

Plan generated in Test terraform-plan #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Single registry

Changes to Outputs
Changes to Outputs:
  + word = "hello"

You can apply this plan to save these new output values to the Terraform
state, without changing any real infrastructure.

Plan applied in Test registry #33

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for apply_when_plan_has_changed

Plan: 1 to add, 0 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.the_string[0] will be created
  + resource "random_string" "the_string" {
      + id          = (known after apply)
      + length      = 5
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Plan not applied in Test changes-only PR comment #59 (Plan has changed)

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for change_then_no_changes

No changes. Your infrastructure matches the configuration.
No changes. Your infrastructure matches the configuration.

Terraform has compared your real infrastructure against your configuration
and found no differences, so no changes are needed.

Plan applied in Test changes-only PR comment #59

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/changes

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + output_string = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Apply Error

Plan: 1 to add, 0 to change, 0 to destroy.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # aws_s3_bucket.my_bucket will be created
  + resource "aws_s3_bucket" "my_bucket" {
      + acceleration_status         = (known after apply)
      + acl                         = "private"
      + arn                         = (known after apply)
      + bucket                      = "hello"
      + bucket_domain_name          = (known after apply)
      + bucket_regional_domain_name = (known after apply)
      + force_destroy               = false
      + hosted_zone_id              = (known after apply)
      + id                          = (known after apply)
      + region                      = (known after apply)
      + request_payer               = (known after apply)
      + tags_all                    = (known after apply)
      + website_domain              = (known after apply)
      + website_endpoint            = (known after apply)

      + versioning {
          + enabled    = (known after apply)
          + mfa_delete = (known after apply)
        }
    }

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

Error applying plan in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/vars
With var files: tests/apply/test.tfvars

With variables

my_var="hello"
complex_input=[
  {
    internal = 2000
    external = 3000
    protocol = "udp"
  },
  {
    internal = 4000
    external = 5000
    protocol = "tcp"
  },
]
Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + complex_output = "2000:3000:udp,4000:5000:tcp"
  + from_var       = "hello"
  + from_varfile   = "monkey"
  + output_string  = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/terraform-cloud in the version-json-2 workspace

Plan: 1 to add, 0 to change, 0 to destroy.
An execution plan has been generated and is shown below.
Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_id.the_id will be created
  + resource "random_id" "the_id" {
      + b64_std     = (known after apply)
      + b64_url     = (known after apply)
      + byte_length = 5
      + dec         = (known after apply)
      + hex         = (known after apply)
      + id          = (known after apply)
    }

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

Plan applied in Test remote backend #165

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for TestLabel

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + complex_output = "8300:8300:tcp"
  + from_var       = "world"
  + from_varfile   = "monkey"
  + output_string  = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/backend_config_12
With backend config files: tests/apply/backend_config_12/backend_config

No changes. Infrastructure is up-to-date.
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, no
actions need to be performed.

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Refresh 1

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 10
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + s = {
      + id               = (known after apply)
      + keepers          = null
      + length           = 10
      + lower            = true
      + min_lower        = 0
      + min_numeric      = 0
      + min_special      = 0
      + min_upper        = 0
      + number           = true
      + override_special = null
      + result           = (known after apply)
      + special          = true
      + upper            = true
    }

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/backend_config_13
With backend config files: tests/apply/backend_config_13/backend_config

No changes. Infrastructure is up-to-date.
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, no
actions need to be performed.

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/vars
With vars: my_var=hello
With var files: tests/apply/test.tfvars

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + complex_output = "8300:8300:tcp"
  + from_var       = "this should be overridden"
  + from_varfile   = "monkey"
  + output_string  = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for pull_request_review

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + output_string = "the_string"

Plan applied in pull_request_review test #79

@dflook
Copy link
Owner Author

dflook commented Sep 25, 2021

Terraform plan for User PAT

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + output_string = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for Refresh 2

Plan: 1 to add, 0 to change, 1 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

  # random_string.my_string must be replaced
-/+ resource "random_string" "my_string" {
      ~ id          = "**********" -> (known after apply)
      ~ length      = 10 -> 20 # forces replacement
      ~ result      = "**********" -> (known after apply)
        # (8 unchanged attributes hidden)
    }

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

Changes to Outputs:
  ~ s = {
      ~ id               = "**********" -> (known after apply)
      ~ length           = 10 -> 20
      ~ result           = "**********" -> (known after apply)
        # (10 unchanged elements hidden)
    }

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan for pre-run

Plan: 1 to add, 0 to change, 0 to destroy. Changes to Outputs.
Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
  + create

Terraform will perform the following actions:

  # random_string.my_string will be created
  + resource "random_string" "my_string" {
      + id          = (known after apply)
      + length      = 11
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

Changes to Outputs:
  + output_string = "the_string"

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/backend_config_12
With backend config: bucket=terraform-github-actions key=backend_config region=eu-west-2

No changes. Infrastructure is up-to-date.
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, no
actions need to be performed.

Plan applied in Test terraform-apply #173

@github-actions
Copy link

github-actions bot commented Sep 25, 2021

Terraform plan in tests/apply/backend_config_13
With backend config: bucket=terraform-github-actions key=backend_config_13 region=eu-west-2

No changes. Infrastructure is up-to-date.
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, no
actions need to be performed.

Plan applied in Test terraform-apply #173

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triggering pull_request_review event...

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triggering pull_request_review event...

It doesn't do anything.
Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Triggering pull_request_review event...

@dflook dflook merged commit 2495eb5 into master Sep 28, 2021
@dflook dflook deleted the version-json branch September 28, 2021 08:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants