Use custom staging dir function for Houdini

[MustafaJafar]

Is there an existing issue for this?

• [X] I have searched the existing issues.

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

Use custom staging dir function for Houdini.

How would you imagine the implementation of the feature?

Not sure, but, I think it's related to ayon core settings:

ayon+settings://core/tools/publish/custom_staging_dir_profiles

Are there any labels you wish to add?

• [X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

I found this on the internal request description:

Based on  transient dir function pipeline.publish.lib.get_transient_dir_info should be
 used everywhere local render folders are used.

[BigRoy]

With the epic to go "lower-level" over Houdini and allowing more freedom/granular control by the studio and artists I feel taking control over the output paths for render ROPs might be counter-intuitive in that goal. @antirotor @dee-ynput - what do you think?

As far as I know this 'custom staging dir' intent has two reasons:

• Define a custom temp directory to render from settings (which seems the opposite of our goals for Houdini?) for the pyblish publishing logic.
• Define whether the render directory is 'persistent' or not, but as soon as we don't use custom staging dirs that kind of becomes irrelevant maybe? Although it does get in the realm of the explicit cleanup plug-in where the source render files get removed on publish?

[antirotor]

Hard to say - it depends on "inheritance". The user story:

Publishing large caches that needs to be stored before published on another (larger) local drive. You might want to set it per product type on Settings level, you might want to override it as Houdini artist locally with some tools, both might want to influence how cleanup is done after publishing. Is it really solve by "lower-level" or is it just another level?