terraform-provider-rhcs
terraform-provider-rhcs copied to clipboard
Update module github.com/hashicorp/terraform-plugin-framework-validators to v0.19.0
This PR contains the following updates:
| Package | Change | Age | Confidence |
|---|---|---|---|
| github.com/hashicorp/terraform-plugin-framework-validators | v0.12.0 -> v0.19.0 |
[!WARNING] Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
hashicorp/terraform-plugin-framework-validators (github.com/hashicorp/terraform-plugin-framework-validators)
v0.19.0
NOTES:
- all: This Go module has been updated to Go 1.24 per the Go support policy. It is recommended to review the Go 1.24 release notes before upgrading. Any consumers building on earlier Go versions may experience errors. (#307)
FEATURES:
- actionvalidator: Introduce new package with declarative validators for action configurations (#302)
- listresourcevalidator: Introduce new package with declarative validators for list resource configurations (#298)
v0.18.0
NOTES:
- all: This Go module has been updated to Go 1.23 per the Go support policy. It is recommended to review the Go 1.23 release notes before upgrading. Any consumers building on earlier Go versions may experience errors. (#276)
BUG FIXES:
- all: Fixed bug with PreferWriteOnlyAttribute validator not running when client is capable of using write-only attributes. (#287)
v0.17.0
FEATURES:
- boolvalidator: Added
PreferWriteOnlyAttributevalidator (#263) - dynamicvalidator: Added
PreferWriteOnlyAttributevalidator (#263) - float32validator: Added
PreferWriteOnlyAttributevalidator (#263) - float64validator: Added
PreferWriteOnlyAttributevalidator (#263) - int32validator: Added
PreferWriteOnlyAttributevalidator (#263) - int64validator: Added
PreferWriteOnlyAttributevalidator (#263) - listvalidator: Added
PreferWriteOnlyAttributevalidator (#263) - mapvalidator: Added
PreferWriteOnlyAttributevalidator (#263) - numbervalidator: Added
PreferWriteOnlyAttributevalidator (#263) - objectvalidator: Added
PreferWriteOnlyAttributevalidator (#263) - resourcevalidator: Added
PreferWriteOnlyAttributevalidator (#263) - stringvalidator: Added
PreferWriteOnlyAttributevalidator (#263)
v0.16.0
FEATURES:
- listvalidator: Added
NoNullValuesvalidator (#245) - mapvalidator: Added
NoNullValuesvalidator (#245) - setvalidator: Added
NoNullValuesvalidator (#245) - dynamicvalidator: New package which contains
types.Dynamicspecific validators (#249)
BUG FIXES:
- Fixed bug with
ConflictsWithandAlsoRequiresvalidators where unknown values would raise invalid diagnostics duringterraform validate. (#251)
v0.15.0
FEATURES:
- ephemeralvalidator: Introduce new package with declarative validators for ephemeral resource configurations (#242)
v0.14.0
NOTES:
- all: This Go module has been updated to Go 1.22 per the Go support policy. It is recommended to review the Go 1.22 release notes before upgrading. Any consumers building on earlier Go versions may experience errors. (#229)
- all: Previously, creating validators with invalid data would result in a
nilvalue being returned and a panic fromterraform-plugin-framework. This has been updated to return an implementation diagnostic referencing the invalid data/validator during config validation. (#235)
FEATURES:
- boolvalidator: Added
Equalsvalidator (#232)
ENHANCEMENTS:
- all: Implemented parameter interfaces for all value-based validators. This allows these validators to be used with provider-defined functions. (#235)
v0.13.0
NOTES:
- 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 (#198)
FEATURES:
- int32validator: New package which contains int32 type specific validators (#222)
- float32validator: New package which contains float32 type specific validators (#222)
ENHANCEMENTS:
- listvalidator: Added
ValueInt32sAreandValueFloat32sArevalidators (#222) - mapvalidator: Added
ValueInt32sAreandValueFloat32sArevalidators (#222) - setvalidator: Added
ValueInt32sAreandValueFloat32sArevalidators (#222)
BUG FIXES:
- Add the attribute from the request to the at-least-one validator's error message (#199)
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
To execute skipped test pipelines write comment /ok-to-test.
Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.
ℹ 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):
- 12 additional dependencies were updated
- The
godirective was updated for compatibility reasons
Details:
| Package | Change |
|---|---|
go |
1.23.0 -> 1.24.0 |
go (toolchain) |
1.23.9 -> 1.24.6 |
github.com/hashicorp/terraform-plugin-framework |
v1.11.0 -> v1.16.1 |
github.com/hashicorp/terraform-plugin-go |
v0.23.0 -> v0.29.0 |
github.com/go-jose/go-jose/v4 |
v4.0.2 -> v4.1.1 |
github.com/go-logr/logr |
v1.4.1 -> v1.4.3 |
github.com/hashicorp/go-hclog |
v1.5.0 -> v1.6.3 |
github.com/hashicorp/go-plugin |
v1.6.0 -> v1.7.0 |
github.com/hashicorp/terraform-registry-address |
v0.2.3 -> v0.4.0 |
github.com/hashicorp/yamux |
v0.1.1 -> v0.1.2 |
github.com/oklog/run |
v1.0.0 -> v1.1.0 |
google.golang.org/genproto/googleapis/rpc |
v0.0.0-20240227224415-6ceb2ff114de -> v0.0.0-20250707201910-8d1bb00bc6a7 |
google.golang.org/grpc |
v1.63.2 -> v1.75.1 |
google.golang.org/protobuf |
v1.36.8 -> v1.36.9 |
Hi @red-hat-konflux[bot]. Thanks for your PR.
I'm waiting for a terraform-redhat member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.
/ok-to-test
/retest-required
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: Once this PR has been reviewed and has the lgtm label, please assign philipwu08 for approval. For more information see the Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@red-hat-konflux[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/unit | 4a5276dcd998ec239419dac4aa5bbc9193f68527 | link | true | /test unit |
| ci/prow/e2e-presubmits-rosa-sts-private-critical-high-presubmit | 4a5276dcd998ec239419dac4aa5bbc9193f68527 | link | true | /test e2e-presubmits-rosa-sts-private-critical-high-presubmit |
| ci/prow/e2e-presubmits-rosa-sts-advanced-critical-high-presubmit | 4a5276dcd998ec239419dac4aa5bbc9193f68527 | link | true | /test e2e-presubmits-rosa-sts-advanced-critical-high-presubmit |
| ci/prow/e2e-presubmits-rosa-hcp-private-critical-high-presubmit | 4a5276dcd998ec239419dac4aa5bbc9193f68527 | link | true | /test e2e-presubmits-rosa-hcp-private-critical-high-presubmit |
Full PR test history. Your PR dashboard.
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.