Houdini: Unify Render Plugins and publish process for render products

[MustafaJafar]

Is there an existing issue for this?

• I have searched the existing issues.

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

As mentioned in this comment ynput/ayon-core#328 (comment) by @BigRoy
Render Creator plugins share most of their code. so, it's better to abstract it to a parent class so this logic is basically re-used for all render creators in Houdini

How would you imagine the implementation of the feature?

Create a parent "CreateRender" class that will be re-used for all render creators in Houdini.

Are there any labels you wish to add?

• I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:

No response

Additional context:

No response

[cuID:AY-5331]

[MustafaJafar]

Hello,
letting you know, that I've changed the issue name from Houdini: Enhance Render Creator Plugins to Houdini: Unify Render Plugins and publish process

Further info:
The rendering process and workflows vary between product types, leading to inconsistencies. For instance, when I adjust settings in the Mantra ROP node, to achieve some result. However, attempting similar configurations in Arnold rop results in errors, and this issue occurs frequently with AOVs.

Here's an example.
I Mantra's AOV setup, it doesn't check if the aov label exists before the before the extension.
It may sound a bug that deserves another issue. But, tbh, I believe we should look at render products as a whole. to achieve consistency.