handle back serialization of floats for default value

Author: ScottSuarez

mmv1/api/type.go

@@ -391,6 +391,21 @@ func (t *Type) MarshalYAML() (interface{}, error) {
 		return nil, err
 	}
 
+	// Fix: Ensure float values (like 0.0) are marshaled as floats (0.0) with !!float tag.
+	// If we don't set the tag, it might be emitted as '0' (int) or '!!int 0.0' (invalid).
+	if _, ok := t.DefaultValue.(float64); ok {
+		for i := 0; i < len(node.Content); i += 2 {
+			if node.Content[i].Value == "default_value" {
+				valNode := node.Content[i+1]
+				if !strings.Contains(valNode.Value, ".") && !strings.Contains(strings.ToLower(valNode.Value), "e") {
+					valNode.Value = valNode.Value + ".0"
+				}
+				valNode.Tag = "!!float"
+				break
+			}
+		}
+	}
+
 	// Special handling for `properties` field.
 	// If the original `properties` slice was explicitly empty (`[]`), `omitempty`
 	// would have removed it during the node encoding. We need to add it back in.

mmv1/products/dataproc/AutoscalingPolicy.yaml

@@ -198,7 +198,7 @@ properties:
               Bounds: [0.0, 1.0].
           - name: scaleUpMinWorkerFraction
             type: Double
-            default_value: 0
+            default_value: 0.0
             description: |
               Minimum scale-up threshold as a fraction of total cluster size before scaling
               occurs. For example, in a 20-worker cluster, a threshold of 0.1 means the autoscaler
@@ -208,7 +208,7 @@ properties:
               Bounds: [0.0, 1.0]. Default: 0.0.
           - name: scaleDownMinWorkerFraction
             type: Double
-            default_value: 0
+            default_value: 0.0
             description: |
               Minimum scale-down threshold as a fraction of total cluster size before scaling occurs.
               For example, in a 20-worker cluster, a threshold of 0.1 means the autoscaler must