Flow name uniqueness

[ribalba]

Flow names need to be unique. Which sort of makes sense from a ui perspective as you don't want flow steps called A, A, A but what I often have is

  - sleep: sleep
    name: sleep
    container: bench-service
    commands:
      - type: console
        command: sleep 10

because the name needs to be unique I keep adding junk to the name. So

name: sleepASDASDASDASDASD

which isn't very nice. Also I would love to do something like

sleep: &sleep
  name: sleep
  container: test-service
  commands:
    - type: console
      command: sleep 10

flow:

  - *sleep

for things that repeat.

I get why names should be unique but do we really want to enforce this? If so, maybe we can add some sort of standard that overrides this.

[ArneTR]

How about not giving a name at all and then the runner fills in a random and incrementing number? This would clobber frontend still though ...

[ribalba]

Maybe remove the requirement for hidden flows?

[ribalba]

I am not a big fan of introducing something random as this might confuse people.