V2.18.0
CLI
- New: Run jobs and services without a Polyaxonfile using
polyaxon runwith--image,--cmd,--env,--cpu,--memory,--gpu,--port,--environment, and--build. - New: Start sandbox services with
polyaxon run --sandbox, using inline options or an existing service Polyaxonfile. - New: Add
--strict-paramsand--no-strict-paramstopolyaxon runandpolyaxon check, andstrict_paramstocheck_polyaxonfile. These set the operation policy without relaxing a strict component or changing preset precedence. - Enhancement: Warn when a Polyaxonfile supplies
version. The field is now optional and no longer selects a validation schema.
Core
- New: Add root execution shortcuts to Polyaxonfiles, including
container,cmd,env,resources,ports,environment,init,connections,sidecars, andvolumes. - Enhancement: Accept undeclared params as context values by default, with or without declared IO. Add
strictParamsto components and operations for opt-in undeclared-name validation. - Enhancement: Accept components, operations, and compiled operations without
version. Preserve supplied values through parsing, compilation, and run storage. - Fix: Record resolved context params alongside declared inputs in
Run.inputs, including runs with no declared inputs. Declared outputs keep their existing recording behavior. - Fix: Handle null-valued params serialized as empty dictionaries without failing scheduler compilation with
Cannot read config_value: {}. - Fix: Retain
strictParamson control-plane workflow parents for child validation, but omit it from resolved specs sent to agents for backward compatibility.
UI
- Enhancement: Improve auto-rendering of inputs/outputs in tables.
Commercial
- Fix: Return
404for malformed integration UUIDs on commercial endpoints, including agent endpoints, instead of failing during request handling.
Compatibility
Undeclared param names, including typos, are now accepted by default. Set strictParams: true to retain undeclared-name checks. In strict mode, explicitly allow extra context values with contextOnly: true. An explicit contextOnly: false requires a matching IO declaration in either mode. Declared IO types, constraints, and required-value validation still apply.
Use CLI and server versions that support the 2.18 policy and compatible SDKs when submitting strictParams. Older CLI and server validators may reject the new field or undeclared params.
Agents do not need to support strictParams; the control plane resolves it before dispatch.
Older CLI and server versions require version: 1.1. Keep it when targeting those versions. V2.18 accepts versioned and versionless Polyaxonfiles.
See the params reference for examples and component/operation precedence.