-
Notifications
You must be signed in to change notification settings - Fork 24
Description
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?
Current integration does expect that one instance render job can have one publish job. But it does make sense to be able to have one publish job for multiple instances.
Because publishing does multiple things, for example change of statuses, it does make sense to integrate rendered files with single publish job for all instances (like we do during local publishing).
Suggested implementation?
This enhancement would require to move responsibility of metadata content preparation to host specific plugins, as it is connected to how instances in metadata file are filled. Which is not "generized" in submit publish job (which is not correct either).
The host specific plugins would prepare the metadata file context for the job. That might require changes in ayon-core too, as we might need to tweak the metadata file content.
NOTE: It would be nice to be able to skip host context (folder path and task name) and not using app from ayon-applications, which would allow to create jobs from hosts like traypublisher.
Describe alternatives you've considered:
No response