Reviewable upload conditioned by webreview tag

[rdelillo]

Is there an existing issue for this?

• I have searched the existing issues and added correct labels.

Please describe the feature you have in mind and explain what the current shortcomings are?

Since https://github.com/ynput/ayon-shotgrid/pull/167/files we changed the way reviewable media might be uploaded to Flow. They used to be part of the pyblish chain of operation, this is now triggered by the reviewable.created event.

My understanding is that this even get propagated only if a valid webreview-tagged representation get added to a Version, which means that now a representation needs to be valid for webreview AND tagged with shotgridreview to be uploaded to Flow.

Do we want such a restriction in the long term ?

Suggested implementation?

No response

Describe alternatives you've considered:

No response

[rdelillo]

This is a regression from 0.5.X but maybe something we actually want to enforce ?
@kalisp @jakubjezek001 @tweak-wtf would be great to get your opinion on this one.

[tweak-wtf]

My understanding is that this even get propagated only if a valid webreview-tagged representation get added to a Version, which means that now a representation needs to be valid for webreview AND tagged with shotgridreview to be uploaded to Flow.

oh good catch.
imho users should be free to decide which representation gets uploaded to which prod-tracker.

i was running a setup where different representations were uploaded. h264 to AYON and some ProRes for SG.
but i ditched that when updating to 0.5.x so now both prod-trackers receive h264 as reviewable with ProRes still being rendered as a "proxy".

so yes, i believe we shouldn't require users to have the same representation in AYON and other prod-trackers.