Filtering folders that are synchronized with Kitsu

[runegan]

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?

Currently if you are syncing with Kitsu, everything you publish to Ayon needs to exist in Kitsu. In some cases you want to have some extra tasks or assets that are not tracked.

If you try to publish a folder/task now, you get this error:

ayon_core.pipeline.publish.publish_plugins.KnownPublishError:  Kitsu id not available in AYON for '/edit'

Forum post with more details:
https://community.ynput.io/t/filtering-folders-that-are-synchronized-with-kitsu/1999/6

Suggested implementation?

I imagine a setting where you can define paths to folders that you do not want to be synced, and then this or any subfolder would not be forced to have a kitsuid.

For example we would have listed "/Edit", "/UE", or "/Assets/Mocap", and any subfolder of these should not need a kitsuid.

Another solution would be to have an option to disable the validation, so it skips all Kitsu related steps without erroring, when no kitsuid is available, but this would likely have some issues.

Describe alternatives you've considered:

Currently we are creating assets in Kitsu, so we are able to publish what we need.

[MustafaJafar]

I think your suggested implementation can be a settings filter that can have these fields with a toggle to set the filter as deny list or white list.