I noticed after setting the path of my caching for Stoke, that for some reason Stoke randomly creates and intermediate sub folder? Is there any way to disable this from happening. It’s posing a problem when we try to develop internal pipeline tools for Stoke specifically into our currently pipeline folder structure. This sub folder that automatically creates itself is a problem.
Any help would be great
As the docs mention:
Each Stoke object will generate a unique random ID upon creation. This ID will be used to create a sub-folder called Stoke_XXXX_YYYY within the Base folder.
How can we disable this from happening upon caching?