Feature Request: finding pipes by guaranteed and documented order of operations

[osher]

the current way forces us to "rename" a pipe in order to pass fittings-config to it.
e.g.

bagpipes:
  my-customized-fitting:
    name:   my-fitting
    custom: setting1
    tuned:  value
  
  my-pipe:
    - my-customized-fitting

Why couldn't it be just:

bagpipes:
  my-fitting:
    custom: setting
    tuned:  value

  my-pipe:
    - my-fitting

[osher]

Edited: fixed wordings...

To do this we need to guarantee order of operations in pipe-finding:

• named pipe exists in memory?
  • yes - use it.
  • no:
    • load pipe factory (according to configured user-fitting + system-fitting, throws not-found error)
    • if fittingDef has no name - use key as name
    • invoke pipe factory with fittingDef