You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Python SDK 2.75 Flex Template: RuntimeValueProvider is being stringified #39499
After upgrading to Apache Beam Python SDK to 2.75.0, runtime parameters passed to a Dataflow Flex Template are not being resolved correctly.
A parameter defined using add_value_provider_argument() is being interpreted as a string representation of RuntimeValueProvider instead of the actual runtime value. There are few args passed which seems to have no issues, only difference is that there is no default value set in all the args but a value is passed expect for the one which has the issue.
Expected behaviour
When a runtime parameter is defined:
class MyOptions(PipelineOptions): @classmethod def _add_argparse_args(cls, parser): parser.add_value_provider_argument( "--vpt_vp_arg", dest="vpt_vp_arg" required=False )
and accessed inside a DoFn:
changed the title [-]Python SDK 2.75 Flex Template: RuntimeValueProvider is being stringified and runtime parameters are treated as unparsed arguments[/-][+]Python SDK 2.75 Flex Template: RuntimeValueProvider is being stringified[/+]on Jul 27, 2026
Activity
[-]Python SDK 2.75 Flex Template: RuntimeValueProvider is being stringified and runtime parameters are treated as unparsed arguments[/-][+]Python SDK 2.75 Flex Template: RuntimeValueProvider is being stringified[/+]Abacn commentedon Aug 5, 2026
Dataflow client migration happened in #37639, in Beam 2.75.0
ValueProvider is mainly used for Dataflow classic templates. If you're building flex templates, value providers are actually not needed