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

Update test for terraform 0.15 #52

Merged
merged 2 commits into from
Apr 14, 2021
Merged

Update test for terraform 0.15 #52

merged 2 commits into from
Apr 14, 2021

Conversation

dflook
Copy link
Owner

@dflook dflook commented Apr 14, 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 Apr 14, 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 #10

@github-actions
Copy link

github-actions bot commented Apr 14, 2021

Terraform plan for SSH Module

Plan: 0 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:

Terraform will perform the following actions:

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

Changes to Outputs:
  + word = "hello"

Plan applied in Test SSH Keys #4

@github-actions
Copy link

Terraform plan in tests/plan/no_changes

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 the remote system(s). As a result, there are no actions to
take.

Plan generated in Test terraform-plan #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 2021

Terraform plan for Single registry

Plan: 0 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:

Terraform will perform the following actions:

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

Changes to Outputs:
  + word = "hello"

Plan applied in Test registry #5

@github-actions
Copy link

github-actions bot commented Apr 14, 2021

Terraform plan for Multiple registries

Plan: 0 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:

Terraform will perform the following actions:

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

Changes to Outputs:
  + word = "hello"

Plan applied in Test registry #5

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 2021

Terraform plan in tests/terraform-cloud in the 15-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 #84

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #7

@dflook
Copy link
Owner Author

dflook commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@github-actions
Copy link

github-actions bot commented Apr 14, 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 #92

@dflook dflook merged commit 20000bc into master Apr 14, 2021
@dflook dflook deleted the 15 branch April 14, 2021 18:11
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