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

Improve parsing of tf files #366

Merged
merged 3 commits into from
Jan 24, 2025
Merged

Improve parsing of tf files #366

merged 3 commits into from
Jan 24, 2025

Conversation

dflook
Copy link
Owner

@dflook dflook commented Jan 23, 2025

The HCL parser we use to retrieve some information about a module sometimes fails to parse files. This could be because the file is malformed in some way, language changes in newer versions, or just a bug in the parser.

This adds a super simple fallback 'parser' for when we can't parse a file normally. It just looks for the critical information we need to continue, like the required_version constraint.

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

github-actions bot commented Jan 23, 2025

Terraform plan for test-changes-only 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 terraform-apply changes-only PR comment #574

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-changes-only 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
+       numeric     = true
+       result      = (known after apply)
+       special     = true
+       upper       = true
    }

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

❌ Plan not applied in Test terraform-apply changes-only PR comment #577 (Plan has changed)

Copy link

github-actions bot commented Jan 23, 2025

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-plan using binary plan #59

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

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 actions using SSH Keys #600

Outputs
word = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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-plan using binary plan #62 (Plan has changed)

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #455

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-registry multiple_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 actions using registry #549

Outputs
word = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #452

Outputs
count = "RfQQ6"

Copy link

github-actions bot commented Jan 23, 2025

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 actions using registry #549

Outputs
word = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #455

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #452

Outputs
count   = "RfQQ6"
foreach = "1hRhyS"

Copy link

github-actions bot commented Jan 23, 2025

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 = "QHhjnQdXrV" -> (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 actions using target and replace #452

Outputs
count   = "w4vSRk6L4b"
foreach = "OIVpAeStuX"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #452

Copy link

github-actions bot commented Jan 23, 2025

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   = "w4vSRk6L4b" -> (known after apply)
!~  foreach = "OIVpAeStuX" -> (known after apply)

✅ Plan applied in Test actions using target and replace #452

Outputs
count   = "vT8h1R50ZH"
foreach = "ETyADrvXs0"

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
output_string = "the_string"

@dflook
Copy link
Owner Author

dflook commented Jan 23, 2025

Terraform plan for test-apply apply_fine_grained_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
+       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-apply #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_label

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       = "world"
+   from_varfile   = "monkey"
+   output_string  = "the_string"

✅ Plan applied in Test terraform-apply #697

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

@dflook
Copy link
Owner Author

dflook commented Jan 23, 2025

Terraform plan for test-apply apply_user_token

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-apply #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_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                         = (known after apply)
+       arn                         = (known after apply)
+       bucket                      = "hello"
+       bucket_domain_name          = (known after apply)
+       bucket_prefix               = (known after apply)
+       bucket_regional_domain_name = (known after apply)
+       force_destroy               = false
+       hosted_zone_id              = (known after apply)
+       id                          = (known after apply)
+       object_lock_enabled         = (known after apply)
+       policy                      = (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)

+       cors_rule (known after apply)

+       grant (known after apply)

+       lifecycle_rule (known after apply)

+       logging (known after apply)

+       object_lock_configuration (known after apply)

+       replication_configuration (known after apply)

+       server_side_encryption_configuration (known after apply)

+       versioning (known after apply)

+       website (known after apply)
    }

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

❌ Error applying plan in Test terraform-apply #697

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_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
+       numeric     = 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
+       numeric          = true
+       override_special = null
+       result           = (known after apply)
+       special          = true
+       upper            = true
    }

✅ Plan applied in Test terraform-apply #697

Outputs
s = {
    id               = "=HMH@GtZqc"
    keepers          = null
    length           = 10
    lower            = true
    min_lower        = 0
    min_numeric      = 0
    min_special      = 0
    min_upper        = 0
    number           = true
    numeric          = true
    override_special = null
    result           = "=HMH@GtZqc"
    special          = true
    upper            = true
}

@dflook
Copy link
Owner Author

dflook commented Jan 23, 2025

OpenTofu plan for test-apply apply_opentofu

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

OpenTofu 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-apply #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_terraform_actions_github_token

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-apply #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_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_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 = "2000:3000:udp,4000:5000:tcp"
+   from_var       = "hello"
+   from_varfile   = "monkey"
+   output_string  = "the_string"

✅ Plan applied in Test terraform-apply #697

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

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-apply/deprecated_var
⚠️ Using deprecated var input. Use the variables input instead.
With vars: my_var=hello
With var files: tests/workflows/test-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
+       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       = "this should be overridden"
+   from_varfile   = "monkey"
+   output_string  = "the_string"

✅ Plan applied in Test terraform-apply #697

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

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply apply_with_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
+       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-apply #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
test = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
test = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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          = "&(_=fl(aTUx" -> 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      = "&(_=fl(aTUx" -> 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 #697

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
s = {
    id               = "F(NrNhtY<PCgCU5dkjh]"
    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           = "F(NrNhtY<PCgCU5dkjh]"
    special          = true
    upper            = true
}

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply destroy_mode_label
💣 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          = "#p*266jS4A?" -> 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      = "#p*266jS4A?" -> 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 #700

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
test = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-cloud/0.13 in the fallback-parse-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 #282

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

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
test = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #455

Outputs
count = "KGLuw"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-apply ephemeral 2

Changes to Outputs.
Changes to Outputs:
!~  v = "non-ephemeral" -> "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 terraform-apply #700

Outputs
v = "hello"

Copy link

github-actions bot commented Jan 23, 2025

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-plan using binary plan #62

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan for test-changes-only 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 terraform-apply changes-only PR comment #577

Copy link

github-actions bot commented Jan 23, 2025

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 actions using target and replace #455

Outputs
count   = "KGLuw"
foreach = "qCLvgj"

Copy link

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

Copy link

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

Copy link

github-actions bot commented Jan 23, 2025

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 = "MNmjW3PXgI" -> (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 actions using target and replace #455

Outputs
count   = "o2wonGUPob"
foreach = "dwzniKR8e9"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-cloud/1.0 in the fallback-parse-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 #282

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

Copy link

github-actions bot commented Jan 23, 2025

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

Outputs
s = "string"

Copy link

github-actions bot commented Jan 23, 2025

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   = "o2wonGUPob" -> (known after apply)
!~  foreach = "dwzniKR8e9" -> (known after apply)

✅ Plan applied in Test actions using target and replace #455

Outputs
count   = "vXqDNaOk1G"
foreach = "nCqetpfWuB"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #455

Copy link

github-actions bot commented Jan 23, 2025

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 Test pull_request_review event #588

Outputs
output_string = "the_string"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #455

Outputs
count = "S5Ug6"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #455

Outputs
count   = "S5Ug6"
foreach = "mQdwcf"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 = "msGKMLzuus" -> (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 actions using target and replace #455

Outputs
count   = "hK4S5Z0hHv"
foreach = "VNuH9wghNL"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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   = "XqD48RKdOO" -> (known after apply)
!~  foreach = "DsIvDRS2sB" -> (known after apply)

✅ Plan applied in Test actions using target and replace #455

Outputs
count   = "SemARAEb9A"
foreach = "TElyVqQuL4"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #455

Outputs
count = "MQRX4"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 actions using target and replace #455

Outputs
count   = "MQRX4"
foreach = "e5QnN3"

Copy link

github-actions bot commented Jan 23, 2025

Terraform plan in tests/workflows/test-target-replace in the fallback-parse 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 = "na603ilCw6" -> (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 actions using target and replace #455

Outputs
count   = "XqD48RKdOO"
foreach = "DsIvDRS2sB"

Copy link

github-actions bot commented Jan 24, 2025

Terraform plan for test-cloud cloud 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.

✅ No changes to apply in Test Terraform cloud #282

Outputs
id  = "72f197d2f3"
len = 5

Copy link

github-actions bot commented Jan 24, 2025

Terraform plan for test-cloud cloud save-plan-changes

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_id.the_id must be replaced
-/+ resource "random_id" "the_id" {
!~      b64_std     = "********" -> (known after apply)
!~      b64_url     = "*******" -> (known after apply)
!~      byte_length = 5 -> 8 # forces replacement
!~      dec         = "************" -> (known after apply)
!~      hex         = "**********" -> (known after apply)
!~      id          = "*******" -> (known after apply)
    }

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

Changes to Outputs:
!~  id  = "**********" -> (known after apply)
!~  len = 5 -> 8

✅ Plan applied in Test Terraform cloud #282

Outputs
id  = "c70dc6a76ade2a06"
len = 8

Copy link

github-actions bot commented Jan 24, 2025

Terraform plan for test-cloud cloud save-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.

✅ No changes to apply in Test Terraform cloud #282

Outputs
id  = "c70dc6a76ade2a06"
len = 8

@dflook dflook merged commit 5d52786 into main Jan 24, 2025
126 checks passed
@dflook dflook deleted the fallback-parse branch January 24, 2025 11:09
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