Please describe the feature you have in mind and explain what the current shortcomings are?
With #32 we added a JOB_ENV_DATA_KEY to start deduplicating the code. But this should start moving out of ayon-deadline into e.g. ayon-core as soon as we have the data structure defined nicely for separate jobs like render, export and publish jobs.
How would you imagine the implementation of the feature?
Make it a constant in ayon-core as soon as we have pinned down that this key is sufficient for re-use in other repos (and also other farm managers and submissions)
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?
With #32 we added a
JOB_ENV_DATA_KEYto start deduplicating the code. But this should start moving out ofayon-deadlineinto e.g.ayon-coreas soon as we have the data structure defined nicely for separate jobs like render, export and publish jobs.How would you imagine the implementation of the feature?
Make it a constant in ayon-core as soon as we have pinned down that this key is sufficient for re-use in other repos (and also other farm managers and submissions)
Are there any labels you wish to add?
Describe alternatives you've considered:
No response
Additional context:
Related to https://github.com/ynput/ayon-core/issues/876