hashicorp / terraform-provider-time

Utility provider that provides Time-Based Resources
https://registry.terraform.io/providers/hashicorp/time/latest
Mozilla Public License 2.0
104 stars 30 forks source link

build(deps): Bump github.com/hashicorp/terraform-plugin-testing from 1.1.0 to 1.2.0 #185

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 1 year ago

Bumps github.com/hashicorp/terraform-plugin-testing from 1.1.0 to 1.2.0.

Release notes

Sourced from github.com/hashicorp/terraform-plugin-testing's releases.

v1.2.0

NOTES:

  • This Go module has been updated to Go 1.19 per the Go support policy. Any consumers building on earlier Go versions may experience errors. (#91)
  • helper/resource: Deprecated PrefixedUniqueId() and UniqueId(). Use the github.com/hashicorp/terraform-plugin-sdk/v2/helper/id package instead. (#96)
  • helper/resource: Deprecated RetryContext(), StateChangeConf, and associated *Error types. Use the github.com/hashicorp/terraform-plugin-sdk/v2/helper/retry package instead. (#96)
  • helper/resource: Deprecated Terraform module-based TestCheckFunc, such as TestCheckModuleResourceAttr. Provider testing should always be possible within the root module of a Terraform configuration. Terraform module testing should be performed with Terraform core functionality or using tooling outside this Go module. (#109)

FEATURES:

  • plancheck: Introduced new plancheck package with interface and built-in plan check functionality (#63)
  • plancheck: Added ExpectResourceAction built-in plan check, which asserts that a given resource will have a specific resource change type in the plan (#63)
  • plancheck: Added ExpectEmptyPlan built-in plan check, which asserts that there are no resource changes in the plan (#63)
  • plancheck: Added ExpectNonEmptyPlan built-in plan check, which asserts that there is at least one resource change in the plan (#63)

ENHANCEMENTS:

  • helper/resource: Added plan check functionality to config and refresh modes with new fields TestStep.ConfigPlanChecks and TestStep.RefreshPlanChecks (#63)
Changelog

Sourced from github.com/hashicorp/terraform-plugin-testing's changelog.

1.2.0 (March 22, 2023)

NOTES:

  • This Go module has been updated to Go 1.19 per the Go support policy. Any consumers building on earlier Go versions may experience errors. (#91)
  • helper/resource: Deprecated PrefixedUniqueId() and UniqueId(). Use the github.com/hashicorp/terraform-plugin-sdk/v2/helper/id package instead. (#96)
  • helper/resource: Deprecated RetryContext(), StateChangeConf, and associated *Error types. Use the github.com/hashicorp/terraform-plugin-sdk/v2/helper/retry package instead. (#96)
  • helper/resource: Deprecated Terraform module-based TestCheckFunc, such as TestCheckModuleResourceAttr. Provider testing should always be possible within the root module of a Terraform configuration. Terraform module testing should be performed with Terraform core functionality or using tooling outside this Go module. (#109)

FEATURES:

  • plancheck: Introduced new plancheck package with interface and built-in plan check functionality (#63)
  • plancheck: Added ExpectResourceAction built-in plan check, which asserts that a given resource will have a specific resource change type in the plan (#63)
  • plancheck: Added ExpectEmptyPlan built-in plan check, which asserts that there are no resource changes in the plan (#63)
  • plancheck: Added ExpectNonEmptyPlan built-in plan check, which asserts that there is at least one resource change in the plan (#63)

ENHANCEMENTS:

  • helper/resource: Added plan check functionality to config and refresh modes with new fields TestStep.ConfigPlanChecks and TestStep.RefreshPlanChecks (#63)
Commits
  • dc69b04 Update changelog
  • 3c3189e helper/resource: Deprecate module-based TestCheckFunc (#109)
  • 31836a5 Add support for Plan Checks with plancheck.ExpectResourceAction, `plancheck...
  • 85bd552 build(deps): Bump github.com/hashicorp/go-hclog from 1.4.0 to 1.5.0 (#104)
  • faec0e7 build(deps): Bump github.com/hashicorp/terraform-plugin-sdk/v2 (#106)
  • 9c304ac build(deps): Bump github.com/zclconf/go-cty from 1.13.0 to 1.13.1 (#103)
  • 5795151 helper/resource: Deprecate non-testing constants, functions, and types (#96)
  • 8de6282 fix goreleaser deprecated build field (#102)
  • 9fb51e2 build(deps): Bump actions/setup-go from 3.5.0 to 4.0.0 (#100)
  • b66d332 build(deps): Bump actions/checkout from 3.3.0 to 3.4.0 (#101)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
github-actions[bot] commented 5 months ago

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.