Define what a WFM does when a configurable parameter is left blank

[ajcraig]

Feature description

Goal: Define what a Workload Fleet Manager (WFM) does when a configurable parameter is left blank. The WFM must not send a null or datatype-specific empty value when no value or default exists. It must omit the parameter from the deployment specification.

Boundary: this feature covers how a WFM creates a deployment specification. It does not define how a device or application handles a parameter that it receives

Provide adequate technical acceptance criteria(s) associated with this feature below:

• When allowEmpty is true and a default value exists, use the default and include the parameter in the deployment specification.
• When allowEmpty is true and no default value exists, omit the parameter from the deployment specification.
• Do not serialize an omitted parameter as null or as a datatype-specific empty value.
• Update the deployment specification text with this rule.

Out of scope for this feature:

• A wire format for null or empty parameters
• How a device or application interprets a parameter it receives
• Datatype-specific handling of blank input, including select and multiselect fields

Although not required, it is highly encouraged to provide feature use-cases below:

No response

Additional information

This feature comes from the "Path forward / looking for guidance" TWG discussion (September 1-4, 2026) and supports margo/specification#212.