With #237 and the addition of the initWorkflow as part of the log, the job directory is defined early in the workflow initialization. With this improvement, some side effects occur with software (eg. DBI) onstart / onend scripts sourcing (when using relative paths), but also with custom global actions.
To fix this, a function get_config_resource_path will be developed to make sure that relative paths set in the config will refer to the actual config working directory (inherited through config$wd) and not the job directory.
With #237 and the addition of the
initWorkflowas part of the log, the job directory is defined early in the workflow initialization. With this improvement, some side effects occur with software (eg. DBI)onstart/onendscripts sourcing (when using relative paths), but also with custom global actions. To fix this, a functionget_config_resource_pathwill be developed to make sure that relative paths set in the config will refer to the actual config working directory (inherited throughconfig$wd) and not the job directory.cc @BastienIRD @juldebar