chore(deps): update module github.com/hashicorp/terraform-plugin-testing to v1.8.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
github.com/hashicorp/terraform-plugin-testing	v1.6.0 -> v1.8.0

---

Release Notes

hashicorp/terraform-plugin-testing (github.com/hashicorp/terraform-plugin-testing)

v1.8.0

Compare Source

FEATURES:

• plancheck: Added ExpectDeferredChange and ExpectNoDeferredChanges checks for experimental deferred action support. (#​331)
• tfversion: Added SkipIfNotPrerelease version check for testing experimental features of prerelease Terraform builds. (#​331)

ENHANCEMENTS:

• helper/acctest: Improve scope of IPv4/IPv6 random address generation in RandIpAddress() (#​305)
• knownvalue: Add TupleExact, TuplePartial and TupleSizeExact checks for dynamic value testing. (#​312)
• tfversion: Ensured Terraform CLI prerelease versions are considered semantically equal to patch versions in built-in checks to match the Terraform CLI versioning policy (#​303)
• helper/resource: Added (TestCase).AdditionalCLIOptions with AllowDeferral option for plan and apply commands. (#​331)

BUG FIXES:

• helper/resource: Fix panic in output state shimming when a tuple is present. (#​310)
• tfversion: Fixed RequireBelow ignoring equal versioning to fail a test (#​303)

v1.7.0

Compare Source

NOTES:

• helper/resource: Error messages generated by the testing logic, which were updated for clarity in this release, are not protected by compatibility promises. While testing logic errors are usable in certain scenarios with ErrorCheck and ExpectError functionality, error messaging checks should be based on provider-controlled messaging or when appropriate to use other testing features such as ExpectNonEmptyPlan instead. (#​238)
• Numerical values in the plan are now represented as json.Number, not float64. Custom plan checks relying upon float64 representation may need altering (#​248)
• plancheck: Deprecated ExpectNullOutputValue and ExpectNullOutputValueAtPath. Use ExpectKnownOutputValue and ExpectKnownOutputValueAtPath with knownvalue.Null instead (#​275)
• plancheck: ExpectKnownValue, ExpectKnownOutputValue and ExpectKnownOutputValueAtPath plan checks are considered experimental and may be altered or removed in a subsequent release (#​276)
• statecheck: ExpectKnownValue, ExpectKnownOutputValue and ExpectKnownOutputValueAtPath state checks are considered experimental and may be altered or removed in a subsequent release (#​276)
• knownvalue: The knownvalue package is considered experimental and may be altered or removed in a subsequent release (#​276)
• all: This Go module has been updated to Go 1.21 per the Go support policy. It is recommended to review the Go 1.21 release notes before upgrading. Any consumers building on earlier Go versions may experience errors (#​300)

FEATURES:

• plancheck: Added ExpectKnownValue plan check, which asserts that a given resource attribute has a defined type, and value (#​248)
• plancheck: Added ExpectKnownOutputValue plan check, which asserts that a given output value has a defined type, and value (#​248)
• plancheck: Added ExpectKnownOutputValueAtPath plan check, which asserts that a given output value at a specified path has a defined type, and value (#​248)
• knownvalue: Introduced new knownvalue package which contains types for working with plan checks and state checks (#​248)
• statecheck: Introduced new statecheck package with interface and built-in state check functionality (#​275)
• statecheck: Added ExpectKnownValue state check, which asserts that a given resource attribute has a defined type, and value (#​275)
• statecheck: Added ExpectKnownOutputValue state check, which asserts that a given output value has a defined type, and value (#​275)
• statecheck: Added ExpectKnownOutputValueAtPath plan check, which asserts that a given output value at a specified path has a defined type, and value (#​275)
• statecheck: Added ExpectSensitiveValue built-in state check, which asserts that a given attribute has a sensitive value (#​275)

BUG FIXES:

• helper/resource: Clarified error messaging from testing failures, especially when using TestStep.PlanOnly: true (#​238)
• helper/resource: Fix detection of provider block declaration in Config, ConfigDirectory, and ConfigFile (#​265)
• helper/resource: Fix detection of terraform block declaration in Config, ConfigDirectory, and ConfigFile (#​265)
• helper/resource: Fixed internal deferred test helpers to properly report file and line information in test failures. (#​292)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[renovate]

ℹ Artifact update notice

File name: go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 14 additional dependencies were updated

Details:

Package	Change
github.com/ProtonMail/go-crypto	v0.0.0-20230923063757-afb1ddc0824c -> v1.1.0-alpha.2
github.com/cloudflare/circl	v1.3.5 -> v1.3.7
github.com/fatih/color	v1.15.0 -> v1.16.0
github.com/hashicorp/go-hclog	v1.5.0 -> v1.6.3
github.com/hashicorp/hc-install	v0.6.1 -> v0.6.4
github.com/hashicorp/hcl/v2	v2.19.1 -> v2.20.1
github.com/hashicorp/terraform-exec	v0.19.0 -> v0.21.0
github.com/hashicorp/terraform-json	v0.18.0 -> v0.22.1
github.com/hashicorp/terraform-plugin-sdk/v2	v2.30.0 -> v2.33.0
github.com/zclconf/go-cty	v1.14.1 -> v1.14.4
golang.org/x/crypto	v0.21.0 -> v0.23.0
golang.org/x/mod	v0.13.0 -> v0.16.0
golang.org/x/sys	v0.18.0 -> v0.20.0
golang.org/x/text	v0.14.0 -> v0.15.0

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.