The config file has a job name! This also solves the "issue" where the job name in the config file is never really used. IT makes more sense if the name in the config is used as the DB key. This means that the path argument the submit api request can be removed
The Job name is extraction during input parsing before the job itself is launched. This CAN be required to be unique and return a "Job already exists"
The config file has a job name! This also solves the "issue" where the job name in the config file is never really used. IT makes more sense if the name in the config is used as the DB key. This means that the path argument the submit api request can be removed
The Job name is extraction during input parsing before the job itself is launched. This CAN be required to be unique and return a "Job already exists"