Toolkit will only create the folders that can be created given a context and fulfil the rules.
Which is to say if you create the folders for a shot, you should only get the folders for that shot and no other shot, unless you have
create_with_parent set to true on the shot folder, in which case all shots will get created when the sequence does.
By default step folders are set to create with their parent, so if you have a step folder in the secondary root, then make sure you set them to
Also in your secondary root, avoid having static folders underneath your dynamic ones, and have your script generate the path using the template and ensure that the remaining folders not covered by the schema exist.
For example your schema might go:
and will have no sub static folders, and your template would be
So your script would ensure it created the
Or another option would be to just have a secondary root folder and no sub folders. Then you can use the template to build the path and you can ensure that the folders are created. However there are two catches here:
- The folders won’t be registered in the path cache (other than the root of the secondary storage) which means you won’t be able to derive context from the paths.
- You won’t be able to use
Context.as_template_fields to generate the field values for resolving the template keys. You would manually have to generate the key values your self, or you could generate them based on a matching template on your primary root and then apply them to your secondary root template.