Co-authored-by: Clément Hector <clement.hector@gmail.com>

Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>

…_plugins

Module kitsu implement pyblish plugins

Co-authored-by: Jakub Trllo <43494761+iLLiCiTiT@users.noreply.github.com>

Co-authored-by: Félix David <felixg.david@gmail.com>

…roval

waiting approval status can be set in project settings

Target farm is being used for rendering, this should better differentiate it.

…d of in prelaunch hook

…nt/OP-2787_Maya-ABC-farm-publishing

…m-publishing' into enhancement/OP-2787_Maya-ABC-farm-publishing

Remote publish requires path to script which is known only on DL node. Injection of env var is required for remote publish.

Checks for exactly 1 out set.

Filters instances from a workfile and marks only these that should be published on a farm.

It probably makes more sense to check specific flag than a family.

deadline family is not used anymore anywhere, filtering on integrate is being done on instance.data["farm"] flag.

This reverts commit 6b71ff1

Not only Deadline could be used for remote publish. DL plugin will be picked only if DL module is enabled.

Doesn't do anything.

Env var created to differentiate launch of Maya on the farm. lib.IS_HEADLESS might be triggered locally, it is not precise enough.

Added same env var to all commands to standardize it a bit.

…variable.

Useful for remote workflows where Site Sync is being used.
When Load reference is used, real root value (c:/project) is replaced with ${OPENPYPE_ROOT_WORK}.