Feature request: Allow pulling package lists from environment variables like REZ_USED_RESOLVE

[yuanmich2]

Describe the problem

The submitters make it difficult to customize the list of rez and conda packages that the worker will pull. It's possible to hardcode the value the package lists in the queue environment or manually type in the correct list in the submitter UI, but hardcoding the value doesn't work well for studios that need many different combinations of packages, and typing the correct value in manually is error prone and not very user friendly.

Proposed Solution

We should be able to set the value of the package lists through an environment variable. For example, "REZ_USED_RESOLVE " is an environment variable for Rez that defines all the resolved packages in the submitter's environment. If we populated the list of needed packages from that, the render worker's environment would pull the same packages as the submitter which would probably help in ensuring that the render succeeds.

Example Use Cases

If a customer is using REZ to manage their workstations and their farm environment, then pulling the list of REZ packages from REZ_USED_RESOLVE would allow them to effortlessly sync their submitting environment with their render environment

[ttblanchard]

Thanks for the feature request!

This is an interesting enhancement with uses beyond Rez I could imagine.

[mwiebe]

We've written up an idea for expressing this in Open Job Description here: OpenJobDescription/openjd-specifications#104