Publish representation with isIntermediate flag in data

[jakubjezek001]

Changelog Description

Publish intermediate file representation with isIntermediate flag in data

Additional info

• Adjusted method parameters in ExporterReview class for better readability.
• Added colorspace parameter to get_representation_data method.

Testing notes:

1. in Nuke activate ayon+settings://nuke/publish/ExtractReviewIntermediates/outputs/0/publish
2. in Nuke publish normal render product type and capture published representation id from integrate.py plugin log.
3. Open AYON console from Tray and use following snippet to check the data of published representation.

from pprint import pprint
from ayon_api import get_representation_by_id

repre = get_representation_by_id(
    [YOUR PROJECT NAME], [PUBLISHED_REPRE_ID],)

pprint(repre)

4. you should be able to find isIntermediate flag within the repre document data keys.

this is follower for #501

[ynbot]

Task linked: AY-5269 Nuke: Publish intermediate files

[moonyuet]

Tested successfully in nuke and our console.

[kalisp]

Why won't we use tag for it? Or maybe I am misunderstanding use case.

[BigRoy]

Why won't we use tag for it? Or maybe I am misunderstanding use case.

I actually had the same question in my mind as @kalisp had there. @jakubjezek001 could you elaborate a bit on that?

[jakubjezek001]

Tags are used only when we publish, and they're not part of the database document. We need to fetch the flagged data from the database during delivery-related tasks.

[BigRoy]

Tags are used only when we publish, and they're not part of the database document. We need to fetch the flagged data from the database during delivery-related tasks.

Sorry - isn't it the case that we're able to add data["tags"] = ["intermediate"] even on the representation? That's what we're asking, right?

Also, I thought having actual supported tags per representation on a lower level already so that in the database we can actually tag things as well (or does it only exist like that on folders?)

The question kind of is - couldn't this be a tag on the representation or whatever. Or does this mean that we might end up flooding with arbitrary data again on the representations that we do start to rely on elsewhere (e.g. in deliveries) that we do not want to be as fluid but prefer to make more strict, almost like attributes or tags, etc. over time?