feature: pipeline run parameters - dynamic choices (HEXA-1620)

[mrivar]

Related PRs:

• feature: pipeline run parameters - dynamic choices (HEXA-1620) #1780
• refactor: parameters into more atomic files openhexa-sdk-python#386 (refactor)
• feat: SDK - pipeline run parameters - dynamic choices (HEXA-1620) openhexa-sdk-python#385

Changes

• Dynamic choices from file: Pipeline parameters can now declare choices=ChoicesFromFile(path, column?) in the SDK. The app resolves those choices at run time by reading a CSV, JSON, or YAML file from the workspace's file storage and returning a flat list of string values.
• New GraphQL query pipelineParameterChoices(workspaceSlug, pipelineVersionId, parameterCode): fetches the resolved choices on demand. The run-pipeline and version-config dialogs use it to populate a Select widget when a parameter has choicesFromFile set.
• Type mismatch warning: When a choices file contains values that cannot be cast to the parameter's declared type (e.g. a string in an int parameter), those options are rendered disabled in the dropdown and a warning lists the invalid values.
• Config type validation from Backend: Saving a pipeline version config or triggering a run now validates that each supplied value matches the parameter's declared type. Returns INVALID_CONFIG on mismatch instead of silently accepting bad data.
  • Note: It used to be only checked in the frontend and during the actual run.
  • Note 2: It is a simpler validation than the one done during the run, just checking types (such as int doesn't get a str value).

How/what to test

1. Create a pipeline that uses parameters with choices=ChoicesFromFile(path, column?) and choices=path (see the linked SDK PR for the API). Upload a matching CSV/JSON/YAML file to the workspace.
2. Open Run pipeline / Set default values — the parameter should show a dropdown populated from the file.
3. Upload a file whose values don't match the parameter type (e.g. strings for an int param) — invalid options should appear greyed out with a warning message below the select.
4. In the version config dialog, set a parameter to a value of the wrong type and save — expect an error.
5. Test error paths: delete the choices file, use a malformed file, or point to a non-existent column — the widget should show an inline error rather than crashing.

Screenshots / screencast

Example with CSV with 2 columns:

• First param has choices=ChoicesFromFile("choices/choices_2_cols.csv"). Not column chosen so it gives an error.
• Second param has choices=ChoicesFromFile("choices/choices_2_cols.csv", "two") so it shows the option of column two.

name,two
asd,two1
qwe,two2
zxc,two3
csv,two4

Warning when a pipeline parameter has invalid choices (e.g.: int/float with a choices file with strings) the invalid options appear disabled:

Error when trying to save an invalid pipeline parameter (e.g.: an int/float pipeline parameter tries to save a string value):

Error when everything goes wrong (in theory this state should be unreachable, but it's a fail safe in case everything goes wrong 🤪)

[mrivar]

Using this file to run my local openhexa-sdk-python and test the changes in it:

docker-compose.override.yaml:

services:
  app:
    volumes:
      - ../openhexa-sdk-python:/openhexa-sdk-python
    entrypoint: ["/bin/bash", "-c", "pip install --user -q -e /openhexa-sdk-python && exec /code/docker-entrypoint.sh \"$@\"", "--"]

[yolanfery]

Solid ! Good to see lot of tests also ☺️

No major concern, just some code quality topics and questions.

Also, we might want to add documentation as part of this PR now that the documentation is in the repo.

[yolanfery]

[Question] Can you please explain this change and the one below in the same file ?

We already have ? on directory, I don't get why we need to add this union type

[mrivar]

It's introduced because otherwise we get an error when running codegen:
https://github.com/BLSQ/openhexa-app/actions/runs/25879781042/job/76056394291?pr=1780
It's just because null and undefined are not considered the same apparently:

  Types of property 'directory' are incompatible.
    Type 'string | null | undefined' is not assignable to type 'string | undefined'.
      Type 'null' is not assignable to type 'string | undefined'. 

[yolanfery]

Great, thanks for the changes, just missing some documentation 🙂

[mrivar]

Great, thanks for the changes, just missing some documentation 🙂

Right! I forgot about that, thanks for reminding me