Possible hook path bug

Pipeline Integrations
1

Hi there,
Can you confirm this bug?
If I’ve got a custom engine (eg a fork of tk-houdini), and then I upload that as a toolkit bundle. I then define the engine location as a “shotgun” type descriptor pointing to this uploaded package. It appears that the {engine} token used in hook paths doesn’t work; it returns “CustomNonProjectEntity01_105” rather than “tk-houdini”.

I am also unable to override the name with the “name” attribute in the descriptor as this isn’t allowed.

eg

engines.tk-houdini.location:
type: shotgun
entity_type: CustomNonProjectEntity01
id: 105
field: sg_payload
version: 35932

Has anyone discovered this issue before? Or have I broken something else along the way :slight_smile:
Thanks
p.

1 Like
2

Hey Patrick

This looks like it’s very similar to this topic?

Happy carry on the conversation there, we didn’t, unfortunately, get to the bottom of it.
I wasn’t able to reproduce it, but it does smell like there is a bug or bad design there somewhere.

Cheers
Phil

2 Likes
3

3 posts were merged into an existing topic: Names for apps/frameworks specified via shotgun descriptors

5

I’ve merged the replies over to the other topic so we can keep the conversation in one place.

Cheers
Phil