Deadline: only explicit submission parameters are propagated

[m-u-r-p-h-y]

Describe the bug

As Deadline changed the behavior of automated submissions and only explicit submission attributes are included and visible in job properties.
It is extremely useful to have these parameters available to fine-tune jobs on the farm.

Example of Nuke job submitted via OpenPype

Example of Nuke job submitted via Deadline:

Most probably we need to provide just empty parameters during publish, which will be filled with some default values by Deadline.

Again it is easy to compare OpenPype vs. Deadline parameters:

OpenPype

Deadline

This is applicable to any host to Deadline submission, not only Nuke . . .

[cuID:OP-4079]

[BigRoy]

Is there any way to query what Plugin Info parameters a Plugin has? :) If so, then in the abstract deadline submitter we could populate the remainder of attributes that aren't defined yet and submit the default values along.

Still. seems like an odd choice to from Deadline.

[BigRoy]

I can confirm the behavior in the screenshots - tested with Deadline Client Version: 10.1.20.3 Release.

So the available Plug-in info parameters are defined in each Plugin's .options file. Looking at the MayaBatch plug-in that's quite a lot, and doing a submission through Deadline itself does not include all of them - there appear to be OCIO settings, renderer specific settings, alembic writing options. A lot of options appear related to specific types of MayaBatch submissions.
Also didn't find a trivial DeadlineCommand or Web service API query which would list the available options for a plug-in. (It does have that for Cloud Plugins however).

So instead of ingesting it with all available options automatically (which was my first thought) I guess it's better to define which attributes we'll at least want to manage in Deadline and make sure we're sending those across. Luckily the data classes with the new abstract submitters should make that trivial. Unfortunately NukeSubmitDeadline isn't refactored yet but for e.g. Maya I believe it would now be a matter of adding them here - We might need to set the default to "" instead of None to ensure the value is submitted along if we'd want that by default.

[BigRoy]

@m-u-r-p-h-y I suspect this is still the case in AYON?

Do we still care? If so, we should transfer this issue to ayon-deadline