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

Add support for partial cloud config block #268

Merged
merged 13 commits into from
Jun 18, 2023
Merged

Add support for partial cloud config block #268

merged 13 commits into from
Jun 18, 2023

Conversation

dflook
Copy link
Owner

@dflook dflook commented Jun 16, 2023

No description provided.

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

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

Triggering pull_request_review event...

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

Terraform plan in tests/workflows/test-cloud/0.13 in the partial-cloud-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 #161

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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 registry #440

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

Terraform plan in tests/workflows/test-cloud/1.0 in the partial-cloud-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 #161

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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 changes-only PR comment #466 (Plan has changed)

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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 changes-only PR comment #466

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

@github-actions
Copy link

github-actions bot commented Jun 16, 2023

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

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 Jun 16, 2023

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

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 Jun 16, 2023

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

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

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

Triggering pull_request_review event...

Copy link
Collaborator

@danielflooktech danielflooktech left a comment

Choose a reason for hiding this comment

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

Triggering pull_request_review event...

@github-actions
Copy link

github-actions bot commented Jun 18, 2023

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

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 Jun 18, 2023

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

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 Jun 18, 2023

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

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 Jun 18, 2023

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

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 Jun 18, 2023

Terraform plan in tests/workflows/test-cloud/partial in the partial-cloud-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 #161

@github-actions
Copy link

github-actions bot commented Jun 18, 2023

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

@dflook dflook merged commit eae2be1 into main Jun 18, 2023
105 checks passed
@dflook dflook deleted the partial-cloud branch June 18, 2023 14:46
@dflook dflook changed the title Add a test for partial cloud config block Add support for partial cloud config block Jun 18, 2023
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