Re-enable Fluid + compute tier validator (#382)

Turns out this was just an issue with Unknown

Author: dglsparsons

vercel/resource_project.go

@@ -31,11 +31,11 @@ import (
 )
 
 var (
-	_ resource.Resource                = &projectResource{}
-	_ resource.ResourceWithConfigure   = &projectResource{}
-	_ resource.ResourceWithImportState = &projectResource{}
-	_ resource.ResourceWithModifyPlan  = &projectResource{}
-	// _ resource.ResourceWithConfigValidators = &projectResource{}
+	_ resource.Resource                     = &projectResource{}
+	_ resource.ResourceWithConfigure        = &projectResource{}
+	_ resource.ResourceWithImportState      = &projectResource{}
+	_ resource.ResourceWithModifyPlan       = &projectResource{}
+	_ resource.ResourceWithConfigValidators = &projectResource{}
 )
 
 func newProjectResource() resource.Resource {
@@ -615,13 +615,11 @@ At this time you cannot use a Vercel Project resource with in-line ` + "`environ
 	}
 }
 
-/*
 func (r *projectResource) ConfigValidators(ctx context.Context) []resource.ConfigValidator {
 	return []resource.ConfigValidator{
 		&fluidComputeBasicCPUValidator{},
 	}
 }
-*/
 
 // Project reflects the state terraform stores internally for a project.
 type Project struct {

vercel/resource_project_test.go

@@ -152,7 +152,7 @@ func TestAcc_ProjectFluidCompute(t *testing.T) {
                     }
                 }
                 `, projectSuffix)),
-				ExpectError: regexp.MustCompile(strings.ReplaceAll("\"standard_legacy\" is not a valid memory type for Fluid compute", " ", `\s*`)),
+				ExpectError: regexp.MustCompile(strings.ReplaceAll("Fluid compute is only supported with the standard or performance CPU types", " ", `\s*`)),
 			},
 			{
 				// check creating a project with Fluid

vercel/resource_project_validators.go

@@ -25,6 +25,13 @@ func (v *fluidComputeBasicCPUValidator) ValidateResource(ctx context.Context, re
 	if resp.Diagnostics.HasError() {
 		return
 	}
+
+	// If ResourceConfig is unknown (computed), skip validation
+	// since we can't determine the configuration's validity during planning.
+	if project.ResourceConfig.IsUnknown() || project.ResourceConfig.IsNull() {
+		return
+	}
+
 	resourceConfig, diags := project.resourceConfig(ctx)
 	if diags.HasError() {
 		resp.Diagnostics.Append(diags...)
@@ -33,6 +40,14 @@ func (v *fluidComputeBasicCPUValidator) ValidateResource(ctx context.Context, re
 	if resourceConfig == nil {
 		return
 	}
+
+	// Note: Due to UnhandledUnknownAsEmpty: true in resourceConfig(),
+	// unknown values are converted to zero values (false, "").
+	// We can't distinguish between explicitly set zero values and unknown values here.
+	// This is acceptable because:
+	// 1. If values are truly unknown, they'll be validated at apply time by the API
+	// 2. If values are explicitly set to zero values, validation should proceed
+
 	if !resourceConfig.Fluid.ValueBool() {
 		return
 	}