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

[dependabot]

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

Release notes

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

v1.3.3

BUG FIXES:

• types/basetypes: Minor reduction of memory allocations for ObjectValue type ToTerraformValue() method, which decreases provider operation durations at scale (#775)
• resource: Prevented panic during planning caused by SetNestedAttribute with nested attribute Default and multiple configured elements (#783)
• tfsdk: Prevented Value Conversion Error diagnostics when using Set() method with base types instead of custom types (#806)
• providerserver: Significantly reduced memory usage for framework data handling operations, especially during the PlanResourceChange RPC (#792)

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:

... (truncated)

Changelog

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

1.3.3 (July 20, 2023)

BUG FIXES:

• types/basetypes: Minor reduction of memory allocations for ObjectValue type ToTerraformValue() method, which decreases provider operation durations at scale (#775)
• resource: Prevented panic during planning caused by SetNestedAttribute with nested attribute Default and multiple configured elements (#783)
• tfsdk: Prevented Value Conversion Error diagnostics when using Set() method with base types instead of custom types (#806)
• providerserver: Significantly reduced memory usage for framework data handling operations, especially during the PlanResourceChange RPC (#792)

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)

... (truncated)

Commits

• cf1f348 Update changelog
• c3cd5bf Update CHANGELOG for #792 (#808)
• 08047be docs: Use arbitrary with map keys and explicit with object attribute names (#...
• 373a6b3 internal/reflect: Use underlying terraform-plugin-go types to validate provid...
• fc2db9e Correct Nested Attributes doc links (#804)
• 41190b2 internal/fwserver: Remove old multiple pass code comments in PlanResourceChan...
• a46d263 internal/fwserver: Prevent PlanResourceChange panic during changed path loggi...
• e036d9f README.md: fix URL on SDK comparison (#794)
• 51c5272 internal/reflection: Migrate reflection tests for struct tags to exported met...
• 9fe2ca5 types/basetypes: Reduce memory allocations of (ObjectValue).ToTerraformValue(...
• 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 #50.