Constant JOB_ENV_DATA_KEY should move out of ayon-deadline

[BigRoy]

Is there an existing issue for this?

• I have searched the existing issues.

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?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

Related to ynput/ayon-core#876

[iLLiCiTiT]

PR https://github.com/ynput/ayon-core/pull/1023/files added FARM_JOB_ENV_DATA_KEY to ayon-core, now we can just use it and remove the JOB_ENV_DATA_KEY from deadline.

I didn't see it being used elsewhere so it should be safe.

[iLLiCiTiT]

BTW created issues so other addons are filling the environment variable keys on their own:

• ftrack Fill environment variables for farm ayon-ftrack#179
• shotgrid Fill environment variables for farm ayon-shotgrid#149
• kitsu Fill environment variables for farm ayon-kitsu#91
• applications Fill environment variables for farm ayon-applications#41