[Core feature] pyflyte run should support a simple json/yaml as input for all parameters

[kumare3]

Motivation: Why do you think this is important?

Today pyflyte run supports passing json/yaml for dataclass/pydantic or json type arguments. But, often times folks just want to pass various parameters are one json/yaml.

This should be Optional It should continue to support existing parameters

Goal: What should the final outcome look like, ideally?

For a workflow like

@workflow
def foo(x : int, y: str, j: Optional[str]) -> ...
      ...

It should be possible to create a yaml like

x: 1
y: hello

input.yaml

and then pass it using

pyflyte run test.py wf --flyte-inputs input.[yaml | json]

Important to note

pyflyte run test.py wf --help

should list all required and non-required parameters. Also required parameters should be checked before calling the remote.

Describe alternatives you've considered

NA

Propose: Link/Inline OR Additional context

No response

Are you sure this issue hasn't been raised already?

• Yes

Have you read the Code of Conduct?

• Yes

[runllm]

Flyte's pyflyte run command now supports passing structured YAML or JSON input files for workflow execution, simplifying the process of providing multiple parameters. This feature allows users to define workflow inputs in a single YAML or JSON file and pass it during execution.

Example:

# input.yaml
x: 1
y: hello

Command:

pyflyte run test.py wf --flyte-input-yaml input.yaml

Would you like more detail?

Sources:

• Flyte 1.6 Release
• Support Yaml / JSON input for pyflyte run
• FlyIn Flytekit Plugin

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!

[kumare3]

@RunLLM The given link handles yaml/json for singular inputs. I am suggesting one input field for all inputs as an option

[runllm]

Flyte's pyflyte run currently supports passing JSON/YAML for specific input types, but not for consolidating all parameters into a single file. Your proposal aims to simplify this by allowing a single YAML/JSON file to define all workflow inputs.

Would you like more detail?

Sources:

• Flyte 1.6 Release
• Can pyflyte run handle files?
• Map task single input limitation

---

This is an AI-generated response and your feedback is appreciated! Please leave a 👍 if this is helpful and 👎 if it is not.

Mention @RunLLM to ask follow-up questions. See runllm.com for more!