I recently noticed that the order in which I define startup scripts for a standalone IS is not the order in which they are executed.

The order in the sever.conf.yaml

StartupScripts:
  CurrentDir:
    command: 'echo script 1'
    readVariablesFromOutput: 'false'        
    directErrorToCommandOutput: false      
    includeCommandOutputInLogs: true       
    #stopServerOnError: true               
  UpdateOverridesServerConfYaml:
    command: 'echo script 2'
    readVariablesFromOutput: 'false'       
    directErrorToCommandOutput: false      
    includeCommandOutputInLogs: true       
    #stopServerOnError: true               
  OptimizeServer:
    command: 'echo script 3'
    readVariablesFromOutput: 'false'       
    directErrorToCommandOutput: false      
    includeCommandOutputInLogs: true       
    #stopServerOnError: true  

The order of execution

So it's actually running scripts 1 > 3 > 2

Any reason for that? Any way of forcing the order? If you have dependencies between scripts you are basically obligated to make one orchestrator scripts and run that on in stead of running the scripts straight from the yaml.

Hello Matthias,

I believe this will be due to the way the yaml is parsed into a structure before we then execute them in series. In this case it looks like its sorting alphabetically, so CurrentDir, OptimizeServer, UpdateOverridesServerConfYaml (1,3,2)

Could you rename those structures too 1CurrentDir, 2OptimizeServer, 3UpdateOverridesServerConfYaml as a workaround? or change the names so they are alphabetic in the order you want to run them in. We can make a doc update to make this behaviour clearer... 

Thanks,

Dom

------------------------------
Dominic Storey
------------------------------

Hi Dominic

It indeed appears to be sorted alphanumericall

------------------------------
Regards
Matthias Blomme
------------------------------