Bump github.com/hashicorp/terraform-plugin-framework from 1.2.0 to 1.3.2

[dependabot]

Bumps github.com/hashicorp/terraform-plugin-framework from 1.2.0 to 1.3.2.

Release notes

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

v1.3.2

BUG FIXES:

• resource/schema: Ensured Default implementations received request Path and have response Diagnostics handled (#778)
• resource/schema: Prevented panics with Default implementations on list, map, and set where no response Diagnostics or PlanValue was returned (#778)
• providerserver: Ensured Terraform CLI interrupts (e.g. Ctrl-c) properly cancel the context.Context of inflight requests (#782)
• providerserver: Prevented caching of unused data and managed resource schemas (#784)

v1.3.1

BUG FIXES:

• datasource/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• provider/metaschema: Ensure nested attribute Equal methods check nested attribute definition equality (#752)
• provider/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• resource/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• types/basetypes: Prevented panics in ListType, MapType, and SetType methods when ElemType field is not set (#714)
• resource/schema: Prevented Value Conversion Error diagnostics for attributes and blocks implementing both CustomType and PlanModifiers fields (#754)
• types/basetypes: Prevented panic with ListTypableWithSemanticEquals and SetTypableWithSemanticEquals when proposed new element count was greater than prior element count (#772)

v1.3.0

NOTES:

• datasource/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• provider/metaschema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• provider/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• resource/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)

ENHANCEMENTS:

• datasource/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• provider/metaschema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• provider/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• resource/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• datasource/schema: Raise validation errors if attempting to use top-level for_each attribute name, which requires special Terraform configuration syntax to be usable by the data source (#704)
• resource/schema: Raise validation errors if attempting to use top-level for_each attribute name, which requires special Terraform configuration syntax to be usable by the resource (#704)
• datasource/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• provider/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• resource/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• all: Improved SDK logging performance when messages would be skipped due to configured logging level (#744)

BUG FIXES:

• datasource/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• provider/metaschema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• provider/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• resource/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• tfsdk: Raise framework errors instead of generic upstream errors or panics when encountering unexpected values with Set() methods (#715)

Changelog

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

1.3.2 (June 28, 2023)

BUG FIXES:

• resource/schema: Ensured Default implementations received request Path and have response Diagnostics handled (#778)
• resource/schema: Prevented panics with Default implementations on list, map, and set where no response Diagnostics or PlanValue was returned (#778)
• providerserver: Ensured Terraform CLI interrupts (e.g. Ctrl-c) properly cancel the context.Context of inflight requests (#782)
• providerserver: Prevented caching of unused data and managed resource schemas (#784)

1.3.1 (June 14, 2023)

BUG FIXES:

• datasource/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• provider/metaschema: Ensure nested attribute Equal methods check nested attribute definition equality (#752)
• provider/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• resource/schema: Ensure nested attribute and block Equal methods check nested attribute and block definition equality (#752)
• types/basetypes: Prevented panics in ListType, MapType, and SetType methods when ElemType field is not set (#714)
• resource/schema: Prevented Value Conversion Error diagnostics for attributes and blocks implementing both CustomType and PlanModifiers fields (#754)
• types/basetypes: Prevented panic with ListTypableWithSemanticEquals and SetTypableWithSemanticEquals when proposed new element count was greater than prior element count (#772)

1.3.0 (June 07, 2023)

NOTES:

• datasource/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• provider/metaschema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• provider/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)
• resource/schema: The Schema type Validate() method has been deprecated in preference of ValidateImplementation() (#699)

ENHANCEMENTS:

• datasource/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• provider/metaschema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• provider/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• resource/schema: Added Schema type ValidateImplementation() method, which performs framework-defined schema validation and can be used in unit testing (#699)
• datasource/schema: Raise validation errors if attempting to use top-level for_each attribute name, which requires special Terraform configuration syntax to be usable by the data source (#704)
• resource/schema: Raise validation errors if attempting to use top-level for_each attribute name, which requires special Terraform configuration syntax to be usable by the resource (#704)
• datasource/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• provider/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• resource/schema: Raise validation errors if attempting to use attribute names with leading numerics (0-9), which are invalid in the Terraform configuration language (#705)
• all: Improved SDK logging performance when messages would be skipped due to configured logging level (#744)

BUG FIXES:

• datasource/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• provider/metaschema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• provider/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• resource/schema: Raise errors with ListAttribute, MapAttribute, ObjectAttribute, and SetAttribute implementations instead of panics when missing required AttributeTypes or ElementTypes fields (#699)
• tfsdk: Raise framework errors instead of generic upstream errors or panics when encountering unexpected values with Set() methods (#715)

Commits

• defe94c Update changelog
• 58b62c8 build(deps): Bump github.com/hashicorp/terraform-plugin-go (#788)
• 44c2fc9 build(deps): Bump github.com/hashicorp/copywrite in /tools (#787)
• f0ede68 internal/fwserver: Delay resource schema caching to occur after GetProviderSc...
• 4ededd7 internal/fwschemadata: Ensure Default implementations receive request Path an...
• 7f6bef5 build(deps): Bump github.com/hashicorp/terraform-plugin-go from 0.15.0 to 0.1...
• b219ea4 internal/testing: Migrate types package to testtypes to reduce import collisi...
• d33e7ae Update changelog
• 1401070 internal/fwserver: Add unit test for PlanResourceChange with CustomType and D...
• e9f48e6 docs: Adjust semantic equality ordering and use stronger wording for overridi...
• Additional commits viewable in compare view

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)

[dependabot]

Superseded by #51.