Bump github.com/hashicorp/terraform-plugin-framework from 1.16.1 to 1.17.0 in the terraform-devex group across 1 directory

[dependabot]

Bumps the terraform-devex group with 1 update in the / directory: github.com/hashicorp/terraform-plugin-framework.

Updates github.com/hashicorp/terraform-plugin-framework from 1.16.1 to 1.17.0

Release notes

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

v1.17.0

NOTES:

• In [email protected], the UseStateForUnknown plan modifier was updated to preserve null values from prior state for unconfigured attributes. This updated version can cause plan inconsistency errors when used on child attributes of a nested attribute that expect UseStateForUnknown to keep the child attributes on new nested objects as <unknown> (known after apply). The new UseNonNullStateForUnknown plan modifier can now be used where child attributes are expecting this pre-1.15.1 behavior. (#1197)

FEATURES:

• action/schema: Added WriteOnly schema field for action schemas. (#1233)
• all: Added a new plan modifier for all types, UseNonNullStateForUnknown that preserves known, non-null, values for unconfigured attributes. This can be used when it is known that an unconfigured value will remain the same after the attribute is updated to a non-null value. (#1242)

BUG FIXES:

• fwserver: update validation list result validation to check if an identity's values are all null (#1230)

Changelog

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

1.17.0 (December 02, 2025)

NOTES:

• In [email protected], the UseStateForUnknown plan modifier was updated to preserve null values from prior state for unconfigured attributes. This updated version can cause plan inconsistency errors when used on child attributes of a nested attribute that expect UseStateForUnknown to keep the child attributes on new nested objects as <unknown> (known after apply). The new UseNonNullStateForUnknown plan modifier can now be used where child attributes are expecting this pre-1.15.1 behavior. (#1197)

FEATURES:

• action/schema: Added WriteOnly schema field for action schemas. (#1233)
• all: Added a new plan modifier for all types, UseNonNullStateForUnknown that preserves known, non-null, values for unconfigured attributes. This can be used when it is known that an unconfigured value will remain the same after the attribute is updated to a non-null value. (#1242)

BUG FIXES:

• fwserver: update validation list result validation to check if an identity's values are all null (#1230)

Commits

• d11e388 Update changelog
• 18140ec all: Add UseNonNullStateForUnknown plan modifier to assist with child neste...
• 44348af build(deps): Bump the github-actions group with 3 updates (#1243)
• 7fb5005 build(deps): Bump golang.org/x/crypto from 0.36.0 to 0.45.0 in /tools (#1241)
• 1df337d build(deps): Bump github.com/hashicorp/terraform-plugin-log (#1240)
• 5310c68 build(deps): Bump golangci/golangci-lint-action (#1238)
• 58c003c build(deps): Bump actions/upload-artifact in the github-actions group (#1234)
• e0355d6 Add support for write-only attributes in actions (#1233)
• 8855023 list: update list result validation to check if identity is fully null (#1230)
• See full diff 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.