Please describe the feature you have in mind and explain what the current shortcomings are?
Each submit_* job has separate env vars that should be passed as job_info env vars. This makes changes to them more difficult (currently noticed by issue with passing Settings variant to DL jobs in Houdini.)
How would you imagine the implementation of the feature?
This should be yanked out to some lib variable to import or to AbstractSubmitDeadline.add_render_job_env_var (not sure if all DCC are implementing that class).
It needs to be checked if all env vars are the same, or any additional could be added separately by DCC implementation.
Are there any labels you wish to add?
[X] I have added the relevant labels to the enhancement request.
Is there an existing issue for this?
Please describe the feature you have in mind and explain what the current shortcomings are?
Each
submit_*job has separate env vars that should be passed as job_info env vars. This makes changes to them more difficult (currently noticed by issue with passing Settings variant to DL jobs in Houdini.)How would you imagine the implementation of the feature?
This should be yanked out to some lib variable to import or to
AbstractSubmitDeadline.add_render_job_env_var(not sure if all DCC are implementing that class).It needs to be checked if all env vars are the same, or any additional could be added separately by DCC implementation.
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
No response