fix: query performance factor is no longer forcenew

Author: burythehammer

provider/pro/resource_rediscloud_pro_database.go

@@ -230,7 +230,6 @@ func ResourceRedisCloudProDatabase() *schema.Resource {
 				Type:        schema.TypeString,
 				Optional:    true,
 				Computed:    true,
-				ForceNew:    true,
 				ValidateFunc: func(val interface{}, key string) (warns []string, errs []error) {
 					v := val.(string)
 					matched, err := regexp.MatchString(`^([2468])x$`, v)

provider/resource_rediscloud_pro_database_qpf_test.go

@@ -130,12 +130,11 @@ func TestAccResourceRedisCloudProDatabase_qpf(t *testing.T) {
 				),
 			},
 
-			// Test plan to ensure query_performance_factor change forces a new resource
+			// Test that query_performance_factor can be updated without forcing replacement
 			{
-				Config:             formatDatabaseConfig(name, testCloudAccountName, password, "2x", `modules = [{ name = "RediSearch" }]`),
-				PlanOnly:           true, // Runs terraform plan without applying
-				ExpectNonEmptyPlan: true, // Ensures that a change is detected
-				Check: resource.ComposeTestCheckFunc(
+				Config: formatDatabaseConfig(name, testCloudAccountName, password, "2x", `modules = [{ name = "RediSearch" }]`),
+				Check: resource.ComposeAggregateTestCheckFunc(
+					resource.TestCheckResourceAttr("rediscloud_subscription_database.example", "name", "example"),
 					resource.TestCheckResourceAttr("rediscloud_subscription_database.example", "query_performance_factor", "2x"),
 				),
 			},