2.11.10

Improvements

Argo Events trigger improvements for parameters with default values

This release fixes an issue where partial or empty argo event payloads would incorrectly overwrite the default values for the parameters of a triggered flow.

For example a flow with

@trigger(events=["params_event"])
class DefaultParamEventFlow(FlowSpec):

    param_a = Parameter(
        name="param_a",
        default="default value A",
    )

    param_b = Parameter(
        name="param_b",
        default="default value B",
    )

will now correctly have the default values for its parameters when triggered by

from metaflow.integrations import ArgoEvent
ArgoEvent('params_event').publish()

or a default value for param_b and the supplied value for param_a when triggered by

ArgoEvent('params_event').publish({"param_a": "custom-value"})

What's Changed

• [Ready for review] replace pull_request_target by @darinyu in #1790
• [bug fix] Flow decorator click option names fix by @valayDave in #1775
• [@kubernetes port] Allow configurable port number by @valayDave in #1793
• Bump vite from 5.0.12 to 5.0.13 in /metaflow/plugins/cards/ui by @dependabot in #1791
• feature: add metadata for argo workflows template owner by @saikonen in #1798
• fix: support default parameter values with argo events by @saikonen in #1797
• release 2.11.10 by @saikonen in #1799

Full Changelog: 2.11.9...2.11.10