terraform-plugin-framework
terraform-plugin-framework copied to clipboard
A next-generation framework for building Terraform providers.
### Module version ``` v1.7.0 ``` ### Use-cases Consider following schema. ```terraform resp.Schema = schema.Schema{ Attributes: map[string]schema.Attribute{ "id": schema.StringAttribute{ Computed: true, PlanModifiers: []planmodifier.String{stringplanmodifier.UseStateForUnknown()}, }, "name": schema.StringAttribute{ Required: true, }, "cities":...
### Module version ``` github.com/hashicorp/terraform-plugin-framework v1.7.0 ``` ### Use-cases I'm trying out the new dynamic types in version 1.7 and encountered a limitation while trying to use a dynamic type...
### Module version ``` 1.6.1 ``` ### Use-cases Terraform 1.8 general availability release is approaching and the framework website documentation and Go package documentation include call outs about it being...
### Module version ``` 1.4.2 ``` ### Use-cases For resources that have no update functionality rather than adding the [resource.RequiresReplace() attribute plan modifier](https://pkg.go.dev/github.com/hashicorp/terraform-plugin-framework/resource#RequiresReplace) in the schema, you would like to...
### Module version ``` v1.6.0 ``` ### Use-cases The upcoming terraform-plugin-testing v1.7.0 will include enhancements that will be directly helpful for provider-defined function testing, including: * Readily available `tfversion.Version1_8_0` variable...
### Module version ``` v1.6.0 ``` ### Use-cases #931 will introduce a new internal interface `fwfunction.ParameterWithValidateImplementation` and `fwfunction.ReturnWithValidateImplementation` that will enable us to implement logic for validating function parameter and...
A `MapValue`, `ListValue`, or `SetValue` with a nil `elementType` is an invalid state, and therefore cannot verify equality with another value. These changes to the `Equal` method now returns `false`...
### Module version ``` v1.6.1 ``` ### Expected Behavior `Equal` handles a nil `elementType`. I'm not sure if the receiver having a nil type should always return `false`, or if...
### Module version ``` v1.6.0 ``` ### Proposal Following #964 and the `v1.7.0` release, we should refactor the parameter `Name` required validation to utilize the `internal/fwfunction` interfaces for validating parameters....