Skip to content

Conversation

@dflook
Copy link
Owner

@dflook dflook commented Jan 9, 2024

Import has been added. Updated to cope with future operation types, such as remove.

dflook added 2 commits January 2, 2024 17:26
Generalise to work with new operations such as import and the upcoming remove
@github-actions
Copy link

github-actions bot commented Jan 9, 2024

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
+       numeric     = 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 #579

Outputs
output_string = "the_string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for always-new SHOULD BE OUTDATED

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
+       numeric     = 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 is outdated

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/sensitive_var
⚠️ Using deprecated var input. Use the variables input instead.
With vars: (sensitive values)

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

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-plan default_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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 applied in Test terraform-plan #654

Outputs
s = "string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/sensitive_variables

With variables

complex             = [
    {
        animals  = [
            "dog",
            "cat",
        ]
        external = 8300
        internal = 8300
        protocol = "tcp"
    },
]
complex_sensitive   = (sensitive value)
my_float            = 3.14
my_int              = 23
my_sensitive_string = (sensitive value)
my_string           = "hello"
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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-plan self-hosted

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.hello will be created
+   resource "random_string" "hello" {
+       id          = (known after apply)
+       length      = 5
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-plan colours

Plan: 3 to add, 1 to change, 3 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
!~  update in-place
-   destroy
-/+ destroy and then create replacement
+/- create replacement and then destroy

Terraform will perform the following actions:

  # aws_s3_object.update will be updated in-place
!~  resource "aws_s3_object" "update" {
!~      content                = "hello" -> "update"
        id                     = "test-plan-colours-test-object"
        tags                   = {}
+       version_id             = (known after apply)
#        (10 unchanged attributes hidden)
    }

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

  # random_string.create_before_delete must be replaced
+/- resource "random_string" "create_before_delete" {
!~      id          = "****" -> (known after apply)
!~      length      = 4 -> 3 # forces replacement
!~      result      = "****" -> (known after apply)
#        (9 unchanged attributes hidden)
    }

  # random_string.delete[0] will be destroyed
  # (because index [0] is out of range for count)
-   resource "random_string" "delete" {
-       id          = "02g" -> null
-       length      = 3 -> null
-       lower       = true -> null
-       min_lower   = 0 -> null
-       min_numeric = 0 -> null
-       min_special = 0 -> null
-       min_upper   = 0 -> null
-       number      = true -> null
-       numeric     = true -> null
-       result      = "02g" -> null
-       special     = true -> null
-       upper       = true -> null
    }

  # random_string.delete_before_create must be replaced
-/+ resource "random_string" "delete_before_create" {
!~      id          = "***" -> (known after apply)
!~      length      = 3 -> 4 # forces replacement
!~      result      = "***" -> (known after apply)
#        (9 unchanged attributes hidden)
    }

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

Changes to Outputs:
+   add    = "hello"
-   delete = "goodbye" -> null
!~  update = "hello" -> "update"

📝 Plan generated in Test terraform-plan #655

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 Jan 9, 2024

Terraform plan for arm64

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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/vars
With var files: tests/workflows/test-plan/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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/single_sensitive_variable
With variables: my_sensitive_string = (sensitive value)

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

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-plan test_plan_1_4

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

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-ssh ssh_key

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

Outputs
word = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-binary-plan apply

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
+       numeric     = 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-binary-plan #9

Outputs
output_string = "the_string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-target-replace plan_targeting

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.

Warning: Resource targeting is in effect

You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.

The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.

📝 Plan generated in Test plan target and replace #403

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace
Targeting resources: random_string.count[0]
With variables: length = 5

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.count[0] will be created
+   resource "random_string" "count" {
+       id          = (known after apply)
+       length      = 5
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (known after apply)
+       special     = false
+       upper       = true
    }

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

Changes to Outputs:
+   count = (known after apply)

Warning: Resource targeting is in effect

You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.

The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.

✅ Plan applied in Test plan target and replace #403

Outputs
count = "nwgoZ"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-target-replace remote_plan_targeting

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.
╷
│ Warning: Resource targeting is in effect
│ 
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│ 		
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

📝 Plan generated in Test plan target and replace #403

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-binary-plan plan_changed

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
+       numeric     = 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 not applied in Test terraform-binary-plan #9 (Plan has changed)

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace in the fix-summary-outputs workspace
Targeting resources: random_string.count[0]
With variables: length = 5

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.count[0] will be created
+   resource "random_string" "count" {
+       id          = (known after apply)
+       length      = 5
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (known after apply)
+       special     = false
+       upper       = true
    }

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

Changes to Outputs:
+   count = (known after apply)
╷
│ Warning: Resource targeting is in effect
│ 
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│ 		
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

✅ Plan applied in Test plan target and replace #403

Outputs
count = "8WQH1"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-apply warnings_hash

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 will be created
+   resource "random_string" "the_string" {
+       id          = (known after apply)
+       length      = 4
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (known after apply)
+       special     = true
+       upper       = true
    }

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

✅ Plan applied in Test terraform-apply #639

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-registry registry_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 registry #499

Outputs
word = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for repository_dispatch

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_password.p will be created
+   resource "random_password" "p" {
+       bcrypt_hash = (sensitive value)
+       id          = (known after apply)
+       length      = 5
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (sensitive value)
+       special     = true
+       upper       = true
    }

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

📝 Plan generated in Respository Dispatch #50

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

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
+       numeric     = 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 #525

Outputs
output_string = "the_string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-cloud/1.0 in the fix-summary-outputs-2 workspace
With var files: tests/workflows/test-cloud/1.0/my_variable.tfvars
With variables: from_variables = "from_variables"

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_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.

Changes to Outputs:
+   default        = "default"
+   from_tfvars    = "from_tfvars"
+   from_variables = "from_variables"

✅ Plan applied in Test Terraform cloud #223

Outputs
default        = "default"
from_tfvars    = "from_tfvars"
from_variables = "from_variables"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-cloud/partial in the fix-summary-outputs-cloud-2 workspace

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_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.

Changes to Outputs:
+   id  = (known after apply)
+   len = 5

✅ Plan applied in Test Terraform cloud #223

Outputs
id  = "8822a306e0"
len = 5

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 Jan 9, 2024

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
+       numeric     = 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 #580

Outputs
output_string = "the_string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-cloud/0.13 in the fix-summary-outputs-2 workspace
With var files: tests/workflows/test-cloud/0.13/my_variable.tfvars
With variables: from_variables = "from_variables"

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 Terraform cloud #223

Outputs
default        = "default"
from_tfvars    = "from_tfvars"
from_variables = "from_variables"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace
Targeting resources: random_string.foreach["hello"]
With variables: length = 6

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.foreach["hello"] will be created
+   resource "random_string" "foreach" {
+       id          = (known after apply)
+       length      = 6
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (known after apply)
+       special     = false
+       upper       = true
    }

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

Changes to Outputs:
+   foreach = (known after apply)

Warning: Resource targeting is in effect

You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.

The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "nwgoZ"
foreach = "DUdjHi"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace
Targeting resources: random_string.foreach["hello"]
Replacing resources: random_string.foreach["hello"], random_string.count[0]
With variables: length = 10

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.foreach["hello"] will be replaced, as requested
-/+ resource "random_string" "foreach" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

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

Changes to Outputs:
!~  foreach = "cauhpmeKbU" -> (known after apply)

Warning: Resource targeting is in effect

You are creating a plan with the -target option, which means that the result
of this plan may not represent all of the changes requested by the current
configuration.

The -target option is not for routine use, and is provided only for
exceptional situations such as recovering from errors or mistakes, or when
Terraform specifically suggests to use it as part of an error message.

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "0U6CnKGFil"
foreach = "rTnMJY54Vh"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace
Replacing resources: random_string.foreach["hello"], random_string.count[0]
With variables: length = 10

Plan: 2 to add, 0 to change, 2 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.count[0] will be replaced, as requested
-/+ resource "random_string" "count" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

  # random_string.foreach["hello"] will be replaced, as requested
-/+ resource "random_string" "foreach" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

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

Changes to Outputs:
!~  count   = "0U6CnKGFil" -> (known after apply)
!~  foreach = "rTnMJY54Vh" -> (known after apply)

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "A1ZnbgP07O"
foreach = "sibnN9OZsr"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace in the fix-summary-outputs workspace
Targeting resources: random_string.foreach["hello"]
With variables: length = 6

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.foreach["hello"] will be created
+   resource "random_string" "foreach" {
+       id          = (known after apply)
+       length      = 6
+       lower       = true
+       min_lower   = 0
+       min_numeric = 0
+       min_special = 0
+       min_upper   = 0
+       number      = true
+       numeric     = true
+       result      = (known after apply)
+       special     = false
+       upper       = true
    }

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

Changes to Outputs:
+   foreach = (known after apply)
╷
│ Warning: Resource targeting is in effect
│ 
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│ 		
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "8WQH1"
foreach = "QfFV1Q"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-apply backend_config_12 backend_config_file

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

Outputs
test = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-apply backend_config_12 backend_config_file

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

Outputs
test = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-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 #639

Outputs
test = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-apply apply_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)
#        (9 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)
#        (11 unchanged elements hidden)
    }

✅ Plan applied in Test terraform-apply #639

Outputs
s = {
    id               = "ea?UiMg+70xr!t]=-cXP"
    keepers          = null
    length           = 20
    lower            = true
    min_lower        = 0
    min_numeric      = 0
    min_special      = 0
    min_upper        = 0
    number           = true
    numeric          = true
    override_special = null
    result           = "ea?UiMg+70xr!t]=-cXP"
    special          = true
    upper            = true
}

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-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 #639

Outputs
test = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for test-apply warnings_text

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 will be created
  + resource "random_string" "the_string" {
      + id          = (known after apply)
      + length      = 4
      + lower       = true
      + min_lower   = 0
      + min_numeric = 0
      + min_special = 0
      + min_upper   = 0
      + number      = true
      + numeric     = true
      + result      = (known after apply)
      + special     = true
      + upper       = true
    }

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

✅ Plan applied in Test terraform-apply #639

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace in the fix-summary-outputs workspace
Targeting resources: random_string.foreach["hello"]
Replacing resources: random_string.foreach["hello"], random_string.count[0]
With variables: length = 10

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.foreach["hello"] will be replaced, as requested
-/+ resource "random_string" "foreach" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

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

Changes to Outputs:
!~  foreach = "5CispvlRSQ" -> (known after apply)
╷
│ Warning: Resource targeting is in effect
│ 
│ You are creating a plan with the -target option, which means that the
│ result of this plan may not represent all of the changes requested by the
│ current configuration.
│ 		
│ The -target option is not for routine use, and is provided only for
│ exceptional situations such as recovering from errors or mistakes, or when
│ Terraform specifically suggests to use it as part of an error message.
╵

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "z6boU2z5tg"
foreach = "lUEhDy1MeF"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-apply/partial_backend
With backend config: key=74620962301
With backend config files: tests/workflows/test-apply/partial_backend/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 #639

Outputs
test = "hello"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-apply/destroy_mode
💣 Planning to destroy all resources

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

Terraform will perform the following actions:

  # random_string.my_string will be destroyed
-   resource "random_string" "my_string" {
-       id          = "LUpAc:r2Gnu" -> null
-       length      = 11 -> null
-       lower       = true -> null
-       min_lower   = 0 -> null
-       min_numeric = 0 -> null
-       min_special = 0 -> null
-       min_upper   = 0 -> null
-       number      = true -> null
-       numeric     = true -> null
-       result      = "LUpAc:r2Gnu" -> null
-       special     = true -> null
-       upper       = true -> null
    }

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

Changes to Outputs:
-   output_string = "the_string" -> null

✅ Plan applied in Test terraform-apply #639

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-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
+       numeric     = 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 applied in Test terraform-plan #655

Outputs
s = "string"

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan for always-new SHOULD BE OUTDATED

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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/always-new

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
+       numeric     = 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 is outdated

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-plan/always-new

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
+       numeric     = 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 #655

@github-actions
Copy link

github-actions bot commented Jan 9, 2024

Terraform plan in tests/workflows/test-target-replace in the fix-summary-outputs workspace
Replacing resources: random_string.foreach["hello"], random_string.count[0]
With variables: length = 10

Plan: 2 to add, 0 to change, 2 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.count[0] will be replaced, as requested
-/+ resource "random_string" "count" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

  # random_string.foreach["hello"] will be replaced, as requested
-/+ resource "random_string" "foreach" {
!~      id          = "**********" -> (known after apply)
!~      result      = "**********" -> (known after apply)
#        (10 unchanged attributes hidden)
    }

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

Changes to Outputs:
!~  count   = "z6boU2z5tg" -> (known after apply)
!~  foreach = "lUEhDy1MeF" -> (known after apply)

✅ Plan applied in Test plan target and replace #403

Outputs
count   = "qMYiJumOeV"
foreach = "Z83OilzsRe"

@dflook dflook merged commit 50cee51 into main Jan 9, 2024
@dflook dflook deleted the fix-summary-outputs branch January 9, 2024 19:15
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.

3 participants