Order of resource profiles in configmap

[michaelmayer2]

When defining launcher.kubernetes.resources.conf in the helm chart like

The resulting configmap seems to "sort" the resource profiles putting the "100 %" at the start:

It would be nice to respect the order of which the resource profiles are put into values.yaml given the fact that it is the order of the profiles in launcher.kubernetes.resources.conf that determines the order the resource profiles are shown in the workbench UI.

[michaelmayer2]

@sebampuero

[michaelmayer2]

Same issue as in #346 but for resource profiles

[michaelmayer2]

After consulting with my favourite LLM it seems that we are using YAML maps for those configuration files in values.yaml. I am wondering if we simply need to change to a list with named properties ?

“YAML maps (dictionaries) are inherently unordered. If you need to maintain order for key-value pairs, you should use a list of items with named properties”

[SamEdwardes]

I agree that it would be better if it wasn't sorted and the order you entered it in was preserved. In the meantime, however, if you need to preserve the order, you can do something like this. By prefixing with a number, the correct order is kept, and then by providing the name value, you can give a user-friendly name.

# values.yaml
config:
  server:
    launcher.kubernetes.resources.conf:
      "01-small":
        name: Small
        cpus: 1
        mem-mb: 1024
      "02-large":
        name: Large
        cpus: 2
        mem-mb: 2048