You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reference: #447
When the framework type system was originally being developed, the value types were introduced with exported fields which also served as the internal details of whether a value was null, unknown, or a known value of a friendlier Go type. It was known that there was the potential for issues, but the simplified developer experience seemed to outweigh the potential for developer issues. Fast forward a few months, this decision appears to have two consequences that the framework maintainers hear about across various forums.
One issue is that the value types directly expose their internal implementation details and support the three states of a Terraform type value: being null, unknown, or a known value. Only one state should ever be set, but provider developers can make a value that is any combination of those states. This makes the framework behavior potentially indeterminate from the provider developer perspective whether, for example, a null AND unknown value becomes null OR unknown as it works its way through the framework.
```go
type ThingResourceModel struct{
Computed types.String `tfsdk:"computed"`
}
func (r ThingResource) Create(ctx context.Context, req resource.CreateResource, resp *resource.CreateResponse) {
var data ThingResourceModel
resp.Diagnostics.Append(req.Plan.Get(ctx, &data)...)
tflog.Trace(ctx, "Data Values", map[string]any{
// Unknown value: types.String{Null: false, Unknown: true, Value: ""}
"computed": plan.Computed,
})
// Maybe some external API responses here, but showing hardcoded updates for
// brevity. This will make the value invalid by enabling Null without
// disabling Unknown.
data.Computed.Null = true
tflog.Trace(ctx, "Data Values", map[string]any{
// Invalid value: types.String{Null: true, Unknown: true, Value: ""}
"computed": data.Computed,
})
// The invalid value will be either null or unknown, depending on the
// type implementation. If unknown, Terraform will error, since unknown
// values are never allowed in state.
resp.Diagnostics.Append(resp.State.Set(ctx, &data)...)
}
```
Another issue is that the default (zero-value) state for an "unset" value type turns into a known value, which is confusing since these values explicitly support being null. This causes Terraform errors which would surface to practitioners (especially when untested) that provider developers then have to troubleshoot the error message containing Terraform's type system details, potentially discover the reason why it is happening by looking at the framework type source code, then figure out a workable solution. It's not intuitive.
```go
type ThingResourceModel struct{
// let's assume this is left unconfigured (null in config and plan)
Optional types.String `tfsdk:"optional"`
}
func (r ThingResource) Create(ctx context.Context, req resource.CreateResource, resp *resource.CreateResponse) {
// Providers can opt to use a single variable that is updated based on an
// external response, however that logic can be more difficult sometimes,
// so it can be easier to split them. Showing the split way to exemplify
// the "unset" problem.
var plan, state ThingResourceModel
resp.Diagnostics.Append(req.Plan.Get(ctx, &plan)...)
tflog.Trace(ctx, "Plan Values", map[string]any{
// Null value: types.String{Null: true, Unknown: false, Value: ""}
"optional": plan.Optional,
})
// Maybe some external API responses here, but intentionally not
// doing any state.Optional setting, which might happen if the
// external response for that data was null for example.
tflog.Trace(ctx, "State Values", map[string]any{
// Zero-value: types.String{Null: false, Unknown: false, Value: ""}
"optional": state.Optional,
})
// The state zero-value will later cause Terraform to error, such as:
// Error: Provider produced inconsistent result after apply
// ... expected cty.NullVal(cty.String), got cty.StringVal("")
// Since the plan value said it would be null.
resp.Diagnostics.Append(resp.State.Set(ctx, &state)...)
}
```
This deprecation of the fields in preference of functions and methods aims to unexport the internal details and treat the value types as immutable once they are created. When provider developers switch over to the new model, any errant changes to the deprecated exported fields will have no effect. A future version will remove the exported fields entirely and switch the zero-value implementation of these values to being null, instead of a known zero-value of the underlying type.
types: The `Bool` type `Null`, `Unknown`, and `Value` fields have been deprecated in preference of the `BoolNull()`, `BoolUnknown()`, and `BoolValue()` creation functions and `IsNull()`, `IsUnknown()`, and `ValueBool()` methods. The fields will be removed in a future release.
3
+
```
4
+
5
+
```release-note:note
6
+
types: The `Float64` type `Null`, `Unknown`, and `Value` fields have been deprecated in preference of the `Float64Null()`, `Float64Unknown()`, and `Float64Value()` creation functions and `IsNull()`, `IsUnknown()`, and `ValueFloat64()` methods. The fields will be removed in a future release.
7
+
```
8
+
9
+
```release-note:note
10
+
types: The `Int64` type `Null`, `Unknown`, and `Value` fields have been deprecated in preference of the `Int64Null()`, `Int64Unknown()`, and `Int64Value()` creation functions and `IsNull()`, `IsUnknown()`, and `ValueInt64()` methods. The fields will be removed in a future release.
11
+
```
12
+
13
+
```release-note:note
14
+
types: The `Number` type `Null`, `Unknown`, and `Value` fields have been deprecated in preference of the `NumberNull()`, `NumberUnknown()`, and `NumberValue()` creation functions and `IsNull()`, `IsUnknown()`, and `ValueBigFloat()` methods. The fields will be removed in a future release.
15
+
```
16
+
17
+
```release-note:note
18
+
types: The `String` type `Null`, `Unknown`, and `Value` fields have been deprecated in preference of the `StringNull()`, `StringUnknown()`, and `StringValue()` creation functions and `IsNull()`, `IsUnknown()`, and `ValueString()` methods. The fields will be removed in a future release.
0 commit comments