When I first implemented the UUID Terraform type, I followed the example fromterraform-provider-aws for durations:Source. This example doesn't quite make sense, or at the least isn't applicable to our use-case, and since it was used as a base for our custom data type, resulted in UUIDs not being validated when written as strings in a configuration.

i.e. This function is called by the plugin SDK, when reading the config.

func (t durationType) ValueFromString(_ context.Context, in types.String) (basetypes.StringValuable, diag.Diagnostics) {       [...]valueString := in.ValueString()if _, err := time.ParseDuration(valueString); err != nil {return DurationUnknown(), diags // Must not return validation errors}       [...]}

Meanwhile, this function is called duringvalidate/plan/apply:

func (v Duration) ValidateAttribute(ctx context.Context, req xattr.ValidateAttributeRequest, resp *xattr.ValidateAttributeResponse) {if v.IsNull() || v.IsUnknown() {return}}

This means if the duration couldn't be parsed, the value becomes unknown, and then is never validated, and so the provider just sees an Unknown value instead of an error diagnostic.

It's worth noting that youcannot remove theIsUnknown check from a validate function, as Terraform purposefully calls validate functions with unknown values when the attribute is set using a variable. The idea being to validate a config before and after any variables are populated. Therefore the only solution here is to return aknown,valid value, if the UUID couldn't be parsed, as to let the validator handle it.

A similar data type is implemented in such a way that meets our use case forarn interraform-provider-aws, which has been used as a guide for this fix:Source. In this provider, if an ARN can't be parsed, a valid & known value is returned fromValueFromString.

More importantly, I made the mistake of not testing the UUID type failing to parse in the context of a resource / data source. I only wrote internal unit tests for the type. This PR adds a test that ensures an error diagnostic is returned if an invalid UUID is provided to a resource/data-source UUID attribute, which tells us the problem is fixed.